Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_test_order

Test a new Binance.US order without placing it by validating order parameters and signature before execution.

Instructions

Test a new order on Binance.US without actually placing it. Validates order parameters and signature without executing the trade.

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_test_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
symbolYesTrading pair symbol (e.g., BTCUSD, ETHUSD)
quantityNoOrder quantity in base asset
stopPriceNoStop price for stop orders
icebergQtyNoIceberg quantity
recvWindowNoReceive window in milliseconds (max 60000)
timeInForceNoTime in force: GTC, IOC, or FOK
quoteOrderQtyNoOrder quantity in quote asset (for MARKET orders)
trailingDeltaNoTrailing delta in BIPS
newClientOrderIdNoUnique client order ID
newOrderRespTypeNoResponse type
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.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does valuable work by disclosing the key non-obvious trait: no trade is executed and only parameter/signature validation occurs, which implicitly signals that signed API credentials are required. It does not mention rate-limit weight, whether test orders count toward order limits, or what a failed validation returns.

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 tight sentences with the non-execution guarantee front-loaded right after the purpose. Every clause earns its place, with only mild redundancy between 'without actually placing it' and 'without executing the trade.'

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

Completeness3/5

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

For a 14-parameter, signature-validating tool with no output schema, the description omits what the response looks like (validation success payload vs. rejection/error) and any authentication or rate-limit context. The rich input schema compensates on parameters, but return-value behavior is left entirely undocumented.

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% across all 14 parameters, with enums documented for side, type, timeInForce, newOrderRespType, and selfTradePreventionMode. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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 and resource ('test a new order on Binance.US') and immediately clarifies scope with 'without actually placing it.' An agent can distinguish this from the real order-placement siblings (binance_us_new_order, binance_us_cust_new_order) from the description alone, though no sibling is named explicitly.

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?

'Test ... without actually placing it' implies the use case: validating an order before committing to a real one. However, it never states the explicit condition for choosing this over binance_us_new_order, nor any exclusions or prerequisites. Usage is inferable but not spelled out.

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