pionex_bot_get_smart_copy_orderQuery a smart copy bot order by ID to retrieve its details and status for tracking or verification.
Get smart copy order
Query a smart copy bot order by ID. Weight: 1.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Language code (e.g. en, zh) | |
| buOrderId | Yes | Bot order ID (UUID, 36 chars) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, covering the safety profile. The description adds 'Weight: 1', useful rate-limit context beyond the annotations, but says nothing about response contents or error behavior.
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?
Very short and front-loaded, with no filler. Minor redundancy in restating the title, but the core sentence and weight note are efficiently placed.
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 simple read-by-ID tool with full schema coverage and rich annotations, this is minimally adequate. It lacks any statement of what the returned order contains or how it relates to the smart-copy workflow, but nothing critical for invocation is missing.
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?
Schema coverage is 100%, so buOrderId (UUID) and lang are fully documented in the schema. The description's 'by ID' adds little beyond the schema's own description, so the baseline 3 is appropriate.
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: 'Query a smart copy bot order by ID.' This distinguishes it from product-type siblings like get_spot_grid_order and get_futures_grid_order by naming the smart copy bot resource. However, it doesn't explicitly contrast with listing tools such as get_bot_orders, so it is clear but lacks explicit sibling differentiation.
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?
There is no guidance on when to use this tool versus alternatives (e.g. get_bot_orders for listing, create/cancel for mutations). The only cue is the implicit 'by ID' lookup, which the agent must infer from the parameter name rather than from prose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.