tradingcli

order_get

Retrieve detailed information for a specific order using its numeric ID or account and client order ID.

Instructions

Get one order by numeric id or by account plus client order id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "order_get"
  }
}

Input Schema

Name	Required	Description	Default
`account`	No
`order_id`	No
`client_order_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only describes the lookup scope but does not disclose error handling, authentication requirements, or what happens if the order is not found. Minimal behavioral context beyond the basic operation.

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, front-loaded sentence with no redundancy, efficiently conveying the core purpose and lookup methods.

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?

For a simple single-order fetch with an output schema, the description covers the core purpose, but leaves ambiguity around optional parameter combinations and precedence. Additional detail about required fields or fallback behavior would improve completeness.

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

Parameters3/5

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

Schema coverage is 0%, but the description does add meaning by clarifying the two identification modes ('numeric id' and 'account plus client order id'). However, it does not fully explain parameter interactions or constraints (e.g., whether order_id can be combined with account, or if client_order_id always requires account to be present).

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 the tool's function with a specific verb ('Get') and resource ('order'), and distinguishes it from sibling tools like 'orders' (which likely lists) by specifying 'one order' and the two lookup mechanisms (numeric id or account plus client order id).

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

Usage Guidelines4/5

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

The description implies this is the tool to use when retrieving a single order by a known identifier, which differentiates it from listing ('orders') and mutation tools ('order_submit', 'order_cancel'). However, it does not explicitly name alternatives or state when not to use it.

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

Deploy Server