Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_new_order

Place new Binance.US trade orders, including limit, market, stop-loss, take-profit, and limit-maker types, by specifying symbol, side, and order type.

Instructions

Place a new trade order on Binance.US. Supports LIMIT, MARKET, STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT, TAKE_PROFIT_LIMIT, and LIMIT_MAKER order types.

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>"
    },
    "name": "binance_us_new_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYesOrder side: BUY or SELL
typeYesOrder type: LIMIT, MARKET, STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT, TAKE_PROFIT_LIMIT, LIMIT_MAKER
priceNoOrder price. Required for LIMIT and LIMIT_MAKER orders.
symbolYesTrading pair symbol (e.g., BTCUSD, ETHUSD)
quantityNoOrder quantity in base asset. Required for most order types.
stopPriceNoStop price. Required for STOP_LOSS_LIMIT and TAKE_PROFIT_LIMIT orders.
icebergQtyNoIceberg quantity for iceberg orders. timeInForce must be GTC.
recvWindowNoReceive window in milliseconds (max 60000).
timeInForceNoTime in force: GTC (Good Till Cancel), IOC (Immediate Or Cancel), FOK (Fill Or Kill). Required for LIMIT orders.
quoteOrderQtyNoOrder quantity in quote asset. Can be used for MARKET orders instead of quantity.
trailingDeltaNoTrailing delta for trailing stop orders in BIPS (1 BIP = 0.01%).
newClientOrderIdNoUnique client order ID. Auto-generated if not provided.
newOrderRespTypeNoResponse type: ACK, RESULT, or FULL. MARKET/LIMIT default to FULL, others to ACK.
selfTradePreventionModeNoSelf-trade prevention mode: EXPIRE_TAKER, EXPIRE_MAKER, EXPIRE_BOTH, NONE.

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

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden but only says it places a new order and lists order types. It does not disclose that this is a real-money mutating operation, authentication requirements, rate limits, error conditions (e.g., insufficient balance, invalid symbol), or what the response contains.

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 tightly worded sentences with the action front-loaded and zero filler. It is efficient, though arguably too terse given the tool's complexity.

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 14-parameter financial mutation tool with no annotations and no output schema, the description should cover authentication, consequences of execution, and response behavior. Instead it leaves the agent with only the schema's parameter documentation and an enum list.

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 all 14 parameters, enums, and conditional requirements (e.g., price required for LIMIT, stopPrice for STOP_LOSS_LIMIT) are already documented in the schema. The description only repeats the order-type enum, adding no meaning beyond structured fields.

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 ("Place a new trade order") and resource (Binance.US) and enumerates the supported order types, which clearly separates it from read/cancel siblings like binance_us_get_order or binance_us_cancel_order. It stops short of distinguishing itself from close variants such as binance_us_test_order or binance_us_cust_new_order.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus binance_us_test_order (dry-run) or binance_us_cust_new_order, and no stated prerequisites like API key permissions, account funding, or symbol restrictions. The agent must infer usage entirely from the tool name.

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