Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_get_order

Fetch details for a specific custodial trade order by rail, symbol, and order ID to review status, quantities, prices, and execution data.

Instructions

Get details of a specific custodial trade order.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

Response includes: symbol, orderId, price, origQty, executedQty, cummulativeQuoteQty, status, timeInForce, type, side, stopPrice, icebergQty, time, updateTime, isWorking, 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>",
      "orderId": "<orderId>"
    },
    "name": "binance_us_cust_get_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.
symbolYesTrading pair (e.g., BTCUSD)
orderIdYesOrder ID to query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / orderId / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / orderId / minimum
      Added value: +-9007199254740991
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden, and it does deliver two substantive facts: the call requires a custodial solution API key, and the response enumerates the returned fields (symbol, orderId, price, status, isWorking, etc.). It still says nothing about failure behavior for an unknown orderId, rate limits, or permission scope, so it is good but not complete.

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?

The purpose sentence comes first, the auth warning is visually isolated, and the response field list is compact. The field enumeration is long but earns its place because no output schema exists; overall there is little wasted text.

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 three-required-parameter read tool with no output schema, the definition covers the essentials: what it returns, which credential tier it needs, and the identifying inputs via the schema. The absence of guidance on error cases and sibling routing is the main remaining gap.

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 the rail, symbol, and orderId parameters are already fully documented, including the uppercase constraint and numeric bounds. The description adds no additional meaning about how these parameters shape the lookup, which is the expected baseline when the schema does the work.

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?

The description uses a specific verb and resource ('Get details of a specific custodial trade order'), and the qualifier 'custodial' distinguishes it from the non-custodial and OTC order lookups in the sibling list. It stops short of naming those alternatives explicitly, so the differentiation is implicit rather than spelled out.

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?

Usage is only implied: an agent gathers that this is the tool for fetching one custodial order when it already has a rail, symbol, and orderId. There is no statement of when to prefer it over binance_us_get_order or binance_us_otc_get_order, and no note on what to do when the order ID is unknown (e.g., use the order-history tool).

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