Retrieve aggregate venue statistics (volume, trades, throughput) and rolling unique-trader counts; public, no credentials needed. Deprecated: use fetch_stats instead.
Deprecated: use fetch_stats. Get aggregate venue statistics (volume, trades, throughput) plus rolling unique-trader counts. Public — no credentials needed.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses a meaningful behavioral trait — the endpoint is public and requires no credentials — which is exactly the kind of auth context an agent needs. It does not, however, mention caching/freshness, rate limits, or the historical counterpart's distinction, so it is strong but not exhaustive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with zero waste. The deprecation warning — the single most decision-relevant fact — is front-loaded before the functional description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, deprecated aggregate-statistics call with no output schema, the description covers purpose, output contents, auth posture, and the migration path. It omits only how it differs in scope from the sibling fetch_stats_history, a minor gap given the deprecation notice.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing for the description to compensate for; the baseline of 4 applies. The description correctly adds no fabricated parameter syntax.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Get aggregate venue statistics') and enumerates the returned metrics (volume, trades, throughput, rolling unique-trader counts). It also immediately flags deprecation and names the replacement, so an agent can distinguish it from fetch_stats without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit routing guidance: 'Deprecated: use `fetch_stats`.' This tells the agent both when not to use this tool and which sibling to use instead, leaving nothing to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.