Retrieve a complete market snapshot with status, quote, order book depth, candles, orders, position, and trades in a single call for full trading context.
Everything at once: status, quote, DOM, candles, orders, position, and trades in a single call. Useful for full context on each turn.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It transparently discloses that the tool combines many data areas into one call, which is the main behavioral trait. The name 'snapshot' and the read-only contents (status, quote, DOM, candles, orders, position, trades) make the non-mutating nature reasonably clear.
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 short sentences deliver the full scope and the intended usage without waste. The key idea, 'everything at once,' is front-loaded and immediately understandable.
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 aggregate snapshot with an output schema available, the description is complete. It names what the tool returns, explains why an agent would use it, and needs no additional disambiguation.
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 has zero parameters, so there is no parameter information to add. A baseline of 4 is appropriate because parameter semantics are not a concern here.
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?
The description clearly states an aggregate retrieval tool: it returns status, quote, DOM, candles, orders, position, and trades in a single call. This directly distinguishes it from the individual sibling tools that cover each area separately.
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?
The description gives a clear usage context: 'Useful for full context on each turn.' It does not explicitly state when NOT to use it or name alternatives, but the implied contrast with the granular sibling tools is straightforward.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.