amazing-binance-mcp

Overview Schema Source Related Servers Discussions Admin

binance_place_oto_order

Place a Binance one-triggers-the-other (OTO) order pair: submits the first order immediately and places the second only after the first fully fills.

Instructions

Place a REAL one-triggers-the-other pair (entry, then follow-up). Real money.

Calls POST /api/v3/orderList/oto (SIGNED, IP weight 1, unfilled-order count 2). The working leg (LIMIT or LIMIT_MAKER) goes on the book immediately. The pending leg is only placed once the working leg is fully filled — until then it sits in PENDING_NEW and does nothing. Cancelling either leg kills the whole list.

Kill-switch. Refused with Error: … trading is disabled … unless the server runs with BINANCE_ALLOW_TRADING=1.

There is no dry-run for a list; binance_test_order validates one order at a time.

Mandatory extras, enforced locally (S2 L3419):

working_type=LIMIT → working_time_in_force;
pending_type=LIMIT → pending_price, pending_time_in_force;
pending_type=STOP_LOSS|TAKE_PROFIT → pending_stop_price and/or pending_trailing_delta;
pending_type=STOP_LOSS_LIMIT|TAKE_PROFIT_LIMIT → pending_price, pending_time_in_force, and pending_stop_price and/or pending_trailing_delta;
pending_type=LIMIT_MAKER → pending_price. A MARKET pending leg is allowed, but only by pending_quantity — Binance does not support quoteOrderQty inside a list, and this server never sends it.

When to Use:

Entry plus a single exit: buy at a limit, and the moment it fills, arm one stop.
Chaining two orders where the second must not exist until the first is done.

When NOT to Use:

When the follow-up should be a target AND a stop — use binance_place_otoco_order.
When both orders should be live at once — that is binance_place_oco_order.

Returns: A confirmation echoing orderListId, contingencyType, listStatusType, listOrderStatus, listClientOrderId and a ### Legs table. A pending leg reported as PENDING_NEW is NOT on the book yet; the table shows exactly what Binance said and nothing more.

Examples: params = {"symbol": "BTCUSDT", "working_type": "LIMIT", "working_side": "BUY", "working_price": "60000.00", "working_quantity": "0.001", "working_time_in_force": "GTC", "pending_type": "LIMIT", "pending_side": "SELL", "pending_quantity": "0.001", "pending_price": "66000.00", "pending_time_in_force": "GTC", "list_client_order_id": "entry-then-target-001"} params = {"symbol": "BTCUSDT", "working_type": "LIMIT_MAKER", "working_side": "BUY", "working_price": "60000.00", "working_quantity": "0.001", "pending_type": "STOP_LOSS", "pending_side": "SELL", "pending_quantity": "0.001", "pending_stop_price": "57000.00"}

Error Handling:

Error: … trading is disabled … → the kill-switch is off; nothing was sent.
-2010 / -1013 / -1111 are balance, filter and precision failures on either leg.
-2021 means the working LIMIT_MAKER would have taken liquidity immediately.
A 5xx or a timeout means the execution status is UNKNOWN — query with binance_get_order_list before retrying; a duplicate entry is real money.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description goes far beyond the sparse annotations (readOnlyHint=false, idempotentHint=false). It discloses that the pending leg sits in PENDING_NEW until the working leg fully fills, cancelling either leg kills the list, a BINANCE_ALLOW_TRADING=1 kill-switch gates execution, there is no list-level dry-run, and 5xx/timeout leaves execution status unknown. This is exactly the behavioral context an agent needs for a real-money operation.

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 long but every block earns its place: API endpoint, execution mechanics, kill-switch, dry-run limitation, mandatory parameter extras, use/non-use guidance, return semantics, examples, and error handling. The 'Real money' warning is front-loaded and the headings make the content scannable rather than bloated.

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

Completeness5/5

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

For a complex, irreversible, real-money tool with an output schema present, the description covers execution semantics, error codes, retry guidance, and parameter interactions. Nothing an agent needs to select or invoke this tool correctly 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?

Despite the 0% schema coverage signal, the description compensates with the mandatory-extras mapping for each pending_type, the MARKET quoteOrderQty restriction, and two complete parameter examples. It does not walk through every optional field such as icebergs or strategy IDs, but those already carry their own schema descriptions and are not needed for a correct base invocation.

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 states a specific verb and resource: it places a real one-triggers-the-other order pair with a working leg and a pending leg. It is unmistakably differentiated from sibling tools by explicitly naming binance_place_otoco_order and binance_place_oco_order as different behaviors.

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

Usage Guidelines5/5

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

The description includes dedicated 'When to Use' and 'When NOT to Use' sections. It explicitly routes to binance_place_otoco_order when both a target and a stop are needed, to binance_place_oco_order when both orders should be live at once, and to binance_test_order for single-order validation, leaving no ambiguity about alternatives.

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

Deploy Server