Cancel an active algorithmic order on Binance Futures USDⓈ-M Contracts by providing the algo order ID. Use it to stop an algo order that should no longer execute.
The Cancel Algo Order API allows users to cancel an active algorithmic order on USDⓈ-M Contracts in Binance Futures.
| Name | Required | Description | Default |
|---|---|---|---|
| algoId | Yes | Algo order ID (e.g., 14511) | |
| recvWindow | No | Time window for request validity |
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 must carry the burden of behavioral disclosure. It indicates the order must be active, but does not disclose side effects (e.g., permanence), required permissions, rate limits, or response behavior. This is a significant gap for a mutating API.
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?
One concise sentence that is front-loaded with the action and scope. No unnecessary words or repetition of the tool name. It is appropriately sized for a simple cancel operation.
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 annotations and no output schema, the description is incomplete. It does not explain return values, error cases, required permissions, or confirm that the order is canceled immediately. For a mutation tool, this lacks crucial operational context.
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 description coverage is 100%, with both 'algoId' and 'recvWindow' having descriptions. The tool description adds no parameter-level detail beyond what the schema already provides, so the baseline score of 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?
The description clearly states the tool cancels an active algorithmic order on USDⓈ-M Contracts in Binance Futures. The verb 'cancel' and resource 'active algorithmic order' are specific, and the USDⓈ-M scope distinguishes it from spot algo order tools like BinanceSpotCancelOpenTWAPOrder.
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 clear context: it is for canceling active algo orders specifically on USDⓈ-M Futures, implying use when an algo order needs to be removed. It doesn't explicitly mention alternatives or exclusions, but the scope differentiates it from spot order cancellation tools. This is clear but not fully explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.