Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_cancel_oco

Cancels an entire OCO order list and both associated legs using a custodial solution API key, returning canceled order details.

Instructions

Cancel an entire OCO (One-Cancels-the-Other) order list.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

This cancels both legs of the OCO order.

Response includes orderListId, orders array, and orderReports with canceled order details.

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": {
      "rail": "<rail>",
      "symbol": "<symbol>",
      "orderListId": "<orderListId>"
    },
    "name": "binance_us_cust_cancel_oco"
  }
}

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.
symbolYesTrading pair (e.g., BTCUSD)
orderListIdYesOCO order list ID to cancel
newClientOrderIdNoNew client order ID for cancel operation
listClientOrderIdNoList client order ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / orderListId / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / orderListId / minimum
      Added value: +-9007199254740991
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the load and does real work: it discloses the custodial auth requirement, that the operation is destructive across both legs, and what the response contains (orderListId, orders, orderReports). It does not cover what happens if a leg is already filled or how partial failure is reported, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded verb phrase, then a prominent auth warning, then the effect and response shape — good ordering with little waste. 'This cancels both legs of the OCO order' partly restates 'entire OCO order list', a minor redundancy.

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

Completeness4/5

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

For a five-parameter mutation tool with no annotations and no output schema, the description supplies the auth precondition, the blast radius of the operation, and the key return fields. Failure-mode behavior (already-filled legs, error semantics) is the remaining gap.

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 each of the five parameters is already documented in the schema, and the description adds no syntax or constraint detail beyond that baseline. The mention of orderListId relates to the response rather than to how to supply the parameter.

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?

States a specific verb and resource ('Cancel an entire OCO order list') and the 'cust' naming plus the custodial-key warning makes clear it is the custodial-side counterpart to binance_us_cancel_oco. It never names that non-custodial sibling explicitly, so differentiation is inferred rather than stated.

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?

The warning 'REQUIRES CUSTODIAL SOLUTION API KEY' sets a precondition for use and implicitly steers non-custodial callers elsewhere. There is no explicit when-to-use/when-not guidance and no mention of when to prefer cancel-specific or symbol-wide cancel tools instead.

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