cancel_order
Cancel an open order by providing its order ID, allowing you to manage and modify trade positions effectively.
Instructions
Cancel an existing open order.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| order_id | Yes |
Cancel an open order by providing its order ID, allowing you to manage and modify trade positions effectively.
Cancel an existing open order.
| Name | Required | Description | Default |
|---|---|---|---|
| order_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose behavioral aspects like whether cancellation is reversible, side effects, or response structure. For a mutation tool, this is insufficient.
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?
The description is very short but front-loaded. However, it is under-specified; a few more sentences could add value without being verbose.
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?
Given no output schema and minimal description, the tool definition lacks completeness for effective use. Critical details like error handling or behavior on non-existent orders are 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?
The single parameter order_id lacks any description in the schema (0% coverage). The description adds no meaning beyond the parameter name, failing to explain how to obtain or format it.
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 the tool cancels an existing open order, using a specific verb and resource. This distinguishes it from siblings like place_order and modify_order.
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?
No guidance is provided on when to use this tool versus alternatives, such as modify_order. No prerequisites or conditions (e.g., order must be open) are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/selvakumarEsra/ibkr-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server