Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_new_oco

Place a new One-Cancels-the-Other order on Binance.US, combining a limit order and stop-loss order so when one triggers, the other is cancelled.

Instructions

Place a new OCO (One-Cancels-the-Other) order on Binance.US. OCO orders combine a limit order with a stop-loss order. When one triggers, the other is automatically cancelled. Note: For SELL OCOs, limit price > stop price. For BUY OCOs, limit price < stop price.

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>",
      "side": "<side>",
      "quantity": "<quantity>",
      "price": "<price>",
      "stopPrice": "<stopPrice>"
    },
    "name": "binance_us_new_oco"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYesOrder side: BUY or SELL
priceYesLimit order price
symbolYesTrading pair symbol (e.g., BTCUSD, ETHUSD)
quantityYesOrder quantity for both legs of the OCO
stopPriceYesStop price that triggers the stop-loss order
recvWindowNoReceive window in milliseconds (max 60000)
trailingDeltaNoTrailing delta in BIPS for the stop leg
stopIcebergQtyNoIceberg quantity for the stop-loss leg
stopLimitPriceNoLimit price for the stop-loss leg. If provided, stopLimitTimeInForce is required.
limitIcebergQtyNoIceberg quantity for the limit leg
newOrderRespTypeNoResponse type: ACK, RESULT, or FULL
listClientOrderIdNoUnique ID for the entire OCO order list
stopClientOrderIdNoUnique ID for the stop-loss leg
limitClientOrderIdNoUnique ID for the limit order leg
stopLimitTimeInForceNoTime in force for stop-limit order: GTC, IOC, or FOK. Required if stopLimitPrice is provided.
selfTradePreventionModeNoSelf-trade prevention mode

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 supplied, so the description bears the full behavioral burden. It correctly conveys that this is a write operation and that the legs are mutually cancelling, but it omits permissions/margin requirements, rate limits, what happens to reserved funds, and what the response contains, which matters for a 16-parameter order-placement tool.

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?

Four short sentences, front-loaded with the action and followed by the OCO mechanics and the price-ordering caveat. Every sentence carries information; no filler or repetition.

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 mutation tool with 16 parameters, no annotations, and no output schema, the description covers purpose, OCO semantics, and the key validation constraint. Gaps remain around optional-leg behavior and what a successful response returns, though the schema's full description coverage offsets much of the parameter 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 coverage is 100% and the schema documents all 16 parameters, so the baseline is 3. The description adds one genuinely useful cross-parameter constraint (the price/stopPrice ordering by side) that the schema does not express, but it says nothing about the optional legs (trailingDelta, iceberg quantities, stopLimitPrice/stopLimitTimeInForce pairing, newOrderRespType).

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?

The description names a specific verb and resource ('Place a new OCO order on Binance.US') and explains what an OCO is, so an agent can distinguish it from plain order placement siblings such as binance_us_new_order. It does not explicitly name those siblings, so it falls short of a 5.

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 states the operational rule that distinguishes the two legs (SELL requires limit price > stop price, BUY requires limit price < stop price), which is real guidance for correct invocation. However it never says when to choose an OCO over a plain order or how it relates to the OCO query/cancel siblings, leaving usage implied rather than explicit.

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