tradingcli

orders

Retrieve paginated trade history for an account, including source agent and idempotency key to trace trade origins.

Instructions

List paginated order history, including source agent and idempotency key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account": "<account>"
    },
    "name": "orders"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`account`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

B3.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the burden. 'List' implies a safe read operation, and 'paginated' hints at limit/offset behavior. However, it does not disclose whether orders are scoped to the required 'account' parameter or how history is ordered. There are no side effects mentioned, but for a list operation that is acceptable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, front-loaded with the core action 'List paginated order history.' Every word adds value, with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The presence of an output schema covers return values, but the description still lacks context about the required 'account' parameter and pagination details. It is adequate for a simple list tool but leaves the agent to inspect the schema for invocation details. Missing usage comparisons further reduce completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does not explain the required 'account' parameter or the 'limit' and 'offset' parameters beyond the vague term 'paginated.' The mention of 'source agent and idempotency key' refers to output fields, not input parameters, providing no semantic help.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'List paginated order history' with a specific verb and resource, and distinguishes this from sibling tools like order_get (single order) and order_submit. It also adds detail with 'including source agent and idempotency key,' which enriches the purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. It does not mention order_get for single orders, order_submit for creating orders, or any exclusions. The agent is left to infer usage from the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server