Data tools tuned for how agents query
This release targets the agent side of the harness: one shared query vocabulary across every tool, and a contract that lets an agent ask for exactly the slice it needs instead of pulling a whole range and discarding most of it.
- One vocabulary across every tool —
queryfor free text,limitfor result count.topKandqare retired, so an agent that has learned one search tool has learned them all. - Ask for a slice, not a range —
limitnow always applies, even alongside a date range, and the newtake_frompicks which end you get (latestby default, orearliest). Sampling both ends of a long window is two cheap calls instead of one oversized one. - Truncation is visible — when your window holds more than was returned,
meta.noticesays so. An agent can narrow the window on purpose rather than reason over a partial answer it did not know was partial. - Mistakes fail loudly — a stale or misspelled parameter now returns an error naming its replacement instead of being quietly dropped, so a wrong call never comes back looking like a valid one.
- Stricter time inputs — dates and timestamps must be real calendar values in
ISO 8601 UTC, and
polymarket_price_historydefaults to720or365points by interval instead of expanding to fill a wide range.
Upgrade your MCP server to 0.7.0
Run npx -y @llmquant/data-mcp@latest, or re-pin to 0.7.0. Calls still sending
topK or q will fail with an error naming the new parameter, and a date range
without an explicit limit now returns that tool's default page instead of the
whole window — pass limit and take_from to say exactly which slice you want.
Per-tool parameters are in the
API reference.