Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_oco_order

Place a custodial OCO order that combines a limit order with a stop-loss so one leg automatically cancels when the other executes.

Instructions

Place a new OCO (One-Cancels-the-Other) order through the custodial solution.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

OCO orders combine a limit order with a stop-loss order. When one executes, the other is automatically canceled.

Price Restrictions:

  • SELL: Limit Price > Last Price > Stop Price

  • BUY: Limit Price < Last Price < Stop Price

Quantity: Both legs must have the same quantity (iceberg qty can differ).

Note: OCO counts as 2 orders against rate limits.

Response includes orderListId, orders array, and orderReports with 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>",
      "side": "<side>",
      "quantity": "<quantity>",
      "price": "<price>",
      "stopPrice": "<stopPrice>"
    },
    "name": "binance_us_cust_oco_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.
sideYesOrder side: BUY or SELL
assetNoAsset for ExpressTrade
priceYesLimit order price
symbolYesTrading pair (e.g., BTCUSD, ETHUSD)
quantityYesOrder quantity (same for both legs)
stopPriceYesStop trigger price
stopIcebergQtyNoIceberg qty for stop leg
stopLimitPriceNoLimit price for stop-limit leg
limitIcebergQtyNoIceberg qty for limit leg
allowExpressTradeNoEnable ExpressTrade
stopClientOrderIdNoUnique ID for the stop leg
limitClientOrderIdNoUnique ID for the limit order
stopLimitTimeInForceNoTime in force for stop-limit leg

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

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it flags the custodial API key prerequisite, explains the one-cancels-the-other side effect, states the price-ordering invariants for BUY vs SELL, and warns that the call consumes two orders of rate limit. It also names the response fields, so the agent knows what comes back despite the absence of an output schema.

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?

Front-loaded with the action and the hard prerequisite warning, then organized into labeled blocks for mechanics, price restrictions, quantity and rate limits. Every line adds operational information an agent would otherwise have to guess.

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 14-parameter, no-annotation, no-output-schema mutation tool, the description covers authentication, ordering constraints, rate-limit cost and the return shape. Minor gaps remain around failure behavior (e.g., whether the stop leg is rejected if the limit leg fails) and the role of allowExpressTrade, but nothing essential to a correct call is missing.

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?

Schema coverage is already 100%, so the schema documents each of the 14 parameters; the description still adds meaning the schema lacks, notably the relational constraint between price, stopPrice and last price, and the fact that iceberg quantities may differ between legs while the base quantity may not. It does not touch the ExpressTrade or client-order-id parameters, leaving those entirely to the schema.

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?

States a specific verb and resource ("Place a new OCO order") and scopes it with "through the custodial solution," which separates it from the non-custodial binance_us_new_oco and from binance_us_cust_new_order. The parenthetical expansion of OCO makes the instrument type unambiguous without opening the schema.

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 description explains OCO mechanics and the price/quantity preconditions that must hold before calling, which is useful usage context. However, it never says when to prefer this over binance_us_cust_new_order or the non-custodial OCO tool, and gives no explicit when-not conditions, so selection still requires inference.

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