Binance MCP Server

cancel_order

Cancel an active order on Binance using its order ID and trading pair. Provides a straightforward way to remove unfilled orders.

Instructions

Cancela una orden por su orderId en el simbolo dado.

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": {
      "symbol": "<symbol>",
      "order_id": "<order_id>"
    },
    "name": "cancel_order"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes
`order_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A3.8/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action without mentioning side effects, irreversibility, authentication requirements, or error behavior. This is insufficient for a mutation tool.

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 sentence that is front-loaded and contains no fluff. Every word contributes to the meaning.

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

Completeness2/5

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

The description conveys the basic action and parameters but provides no information about return values, errors, or post-conditions. Given the absence of an output schema and annotations, this is functionally incomplete for an agent to fully anticipate the tool's behavior.

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

Parameters4/5

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

The schema has 0% description coverage, but the description clarifies that order_id is the identifier of the order to cancel and symbol is the trading symbol. This adds meaningful semantics beyond the raw schema, though it lacks deeper constraints or format details.

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 uses the specific verb 'Cancela' (cancels) with the resource 'orden' (order), and specifies the exact means ('por su orderId en el simbolo dado'). This clearly distinguishes it from sibling tools like place_order and cancel_all_orders.

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 clearly implies the use case: you need an orderId and a symbol to cancel a specific order. It does not explicitly mention alternatives or exclusions, but the context is unambiguous, so a 4 is appropriate.

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

Deploy Server