Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cancel_replace

Cancel an existing order and place a replacement on the same symbol atomically, enabling you to modify order parameters without exposing the position between orders.

Instructions

Cancel an existing order and place a new order on the same symbol atomically. This is useful for modifying order parameters.

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>",
      "type": "<type>",
      "cancelReplaceMode": "<cancelReplaceMode>"
    },
    "name": "binance_us_cancel_replace"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYesOrder side: BUY or SELL
typeYesOrder type for the new order
priceNoPrice for new order
symbolYesTrading pair symbol (e.g., BTCUSD)
quantityNoQuantity for new order
stopPriceNoStop price for new order
icebergQtyNoIceberg quantity for new order
recvWindowNoReceive window in milliseconds (max 60000)
timeInForceNoTime in force for new order
cancelOrderIdNoOrder ID to cancel. Either this or cancelOrigClientOrderId required.
quoteOrderQtyNoQuote order quantity for new order
trailingDeltaNoTrailing delta for new order
newClientOrderIdNoClient order ID for the new order
newOrderRespTypeNoResponse type for new order
cancelReplaceModeYesSTOP_ON_FAILURE: Don't place new order if cancel fails. ALLOW_FAILURE: Place new order even if cancel fails.
cancelRestrictionsNoCancel restrictions
cancelNewClientOrderIdNoClient order ID for the cancel
cancelOrigClientOrderIdNoClient order ID to cancel. Either this or cancelOrderId required.
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

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden for a destructive, real-money mutation. "Atomically" is the one genuine behavioral trait disclosed, but there is nothing about required permissions, what happens to fills already on the cancelled order, failure/partial-failure behavior, or rate limits.

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?

Two short sentences with the core operation front-loaded; nothing is padded. The second sentence is thin but does add a use-case hint, so it roughly earns its place.

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

Completeness2/5

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

For a 19-parameter, four-required-parameter mutation tool with no annotations and no output schema, the description is far too thin. It never explains the required cancelReplaceMode trade-off, order-identification requirements, or response handling, leaving the agent to reconstruct behavior from schema fields alone.

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% with 19 documented parameters including seven enums, so the schema already does the explanatory work. The description adds no meaning beyond the schema, giving the baseline 3 for high-coverage schemas.

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 compound action (cancel an existing order and place a new order) on the same symbol, which is more precise than a plain cancel. It does not name or contrast with the sibling cancel tools (e.g., binance_us_cancel_order), so an agent must infer the distinction from the name alone.

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?

"This is useful for modifying order parameters" implies the when-to-use case (amend an order rather than cancel-then-recreate), but the guidance is vague and there are no when-not conditions, no mention of when to prefer cancel_order plus new_order, and no note on prerequisites such as the need for an existing open order.

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