Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_new_order

Places new custodial Binance.US trade orders, including limit, market, stop, and take-profit types, with optional ExpressTrade auto-funding when sub-account balance is insufficient.

Instructions

Place a new trade order through the custodial solution.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

Supported order types:

  • LIMIT: Requires timeInForce, quantity, price

  • MARKET: Requires quantity OR quoteOrderQty

  • STOP_LOSS: Requires quantity, stopPrice (executes as MARKET when triggered)

  • STOP_LOSS_LIMIT: Requires timeInForce, quantity, price, stopPrice

  • TAKE_PROFIT: Requires quantity, stopPrice (executes as MARKET when triggered)

  • TAKE_PROFIT_LIMIT: Requires timeInForce, quantity, price, stopPrice

  • LIMIT_MAKER: Requires quantity, price (POST-ONLY order)

ExpressTrade Feature: When allowExpressTrade=true and custodial sub-account balance is insufficient, the full amount will be automatically transferred from the custodial partner.

Response includes: symbol, orderId, status, type, side, price, quantity, executedQty, and expressTradeFlag

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

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.
sideYesOrder side: BUY or SELL
typeYesOrder type
assetNoAsset for ExpressTrade (the asset being sold)
priceNoOrder price (required for LIMIT orders)
symbolYesTrading pair (e.g., BTCUSD, ETHUSD)
quantityNoOrder quantity in base asset
stopPriceNoStop/trigger price for stop orders
icebergQtyNoIceberg order quantity
timeInForceNoGTC (Good Til Canceled), IOC (Immediate or Cancel), FOK (Fill or Kill)
quoteOrderQtyNoOrder quantity in quote asset (MARKET orders only)
allowExpressTradeNoEnable ExpressTrade for auto-funding

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.3/5.0
Behavior4/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 well: it flags the custodial API key requirement, discloses that ExpressTrade will automatically move funds from the custodial partner when the sub-account is short, notes LIMIT_MAKER is post-only, and explains that STOP_LOSS/TAKE_PROFIT execute as MARKET on trigger. It omits rate-limit/weight behavior and failure handling for rejected orders.

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?

Front-loaded with purpose and the blocking credential requirement, then organized as a scannable per-type requirement list. Slightly verbose in places and it partly restates information the schema already carries per-field, but no bullet is wasted.

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 12-parameter, unannotated mutation tool with no output schema, the description covers the essentials: credential requirement, per-type parameter rules, the ExpressTrade side effect, and the response fields. Remaining gaps are secondary — error behavior and the asset parameter's role in ExpressTrade.

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 100%, so baseline is 3, but the description adds real value by consolidating the conditional, per-order-type required-parameter sets (e.g. LIMIT needs timeInForce+quantity+price) that the schema documents only piecemeal. It does not mention that the 'asset' parameter matters for the ExpressTrade path, leaving one dependency to be inferred.

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 first sentence names a specific verb and resource ('Place a new trade order') and scopes it to the custodial solution, which is what separates it from the non-custodial binance_us_new_order sibling. The API-key banner reinforces the custodial-only scope, so an agent can route correctly 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 Guidelines4/5

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

The per-order-type requirement table effectively tells the agent which parameter combination selects each order type, and the ExpressTrade paragraph explains when auto-funding kicks in. It stops short of explicit routing guidance, though — no mention of using binance_us_test_order first, or of when to prefer the non-custodial new_order sibling.

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