Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cancel_oco

Cancel an entire OCO order on Binance.US by specifying the trading pair and order list or client order IDs; cancelling either leg cancels the whole OCO.

Instructions

Cancel an entire OCO order on Binance.US. Cancelling any individual leg will cancel the entire OCO.

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>"
    },
    "name": "binance_us_cancel_oco"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTrading pair symbol (e.g., BTCUSD)
recvWindowNoReceive window in milliseconds (max 60000)
orderListIdNoThe order list ID to cancel
newClientOrderIdNoNew client order ID for this cancel request
listClientOrderIdNoThe list client order ID to cancel

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden for a destructive mutation. It usefully discloses the cascade semantics (any leg cancel kills the whole OCO), but says nothing about authentication requirements, behavior when the order list does not exist or is already filled, or which identifiers are mandatory.

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?

Two short sentences with zero waste; the destructive scope is front-loaded and the caveat follows. Nothing extraneous to trim.

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?

A dangerous mutation with no annotations and no output schema needs more: error behavior on unknown or already-filled list IDs, and how to disambiguate the identifier parameters, are unaddressed. The schema covers parameters well, but the behavioral envelope is thin.

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 description coverage is 100%, so the baseline is 3. The description adds no guidance on whether the OCO is targeted by orderListId, listClientOrderId, or both, despite only symbol being required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Cancel an entire OCO order on Binance.US'), which is clearly distinct from order-cancel and cancel-all siblings. It stops short of naming the alternative cancel tools, so the agent must infer the routing itself.

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

Usage Guidelines3/5

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

Usage is implied by the verb: use this to kill a whole OCO rather than a single order. The note that cancelling any individual leg cancels the entire OCO indirectly hints that a single-order cancel cannot target one leg, but no sibling is named and no when-not guidance is given.

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

Deploy Server

Other Tools