Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_get_order

Query the status of a specific Binance.US order by order ID or original client order ID to track execution and confirm its current state.

Instructions

Query the status of a specific order on Binance.US. Either orderId or origClientOrderId must be provided.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesTrading pair symbol (e.g., BTCUSD)
orderIdNoThe order ID to query
recvWindowNoReceive window in milliseconds (max 60000)
origClientOrderIdNoThe original client order ID to query

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
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 behavioral burden. It implies a read-only status query and gives one identifier constraint, but it does not mention authentication requirements, rate limits, error behavior, or what happens if both identifiers are supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences with the core purpose first and the identifier constraint second. There is no redundant or filler wording.

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 four-parameter lookup tool with no annotations and no output schema, the definition covers the essential action and identifier requirement but leaves return behavior and order-type distinctions unaddressed. It is minimally adequate but thin for an agent that needs to interpret results or distinguish sibling order-query tools.

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 description coverage is 100%, so the parameter descriptions already do most of the work. The description adds an important cross-parameter constraint that is not encoded in the schema: either orderId or origClientOrderId must be provided, even though neither is marked required.

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 gives a specific verb and resource: query the status of a specific order on Binance.US. It is clear what the tool does, but it does not distinguish itself from sibling lookup tools such as binance_us_cust_get_order or binance_us_otc_get_order.

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?

The description states that either orderId or origClientOrderId must be provided, which is useful calling guidance. However, it gives no explicit when-to-use guidance, no exclusions, and no direction toward alternative tools for custody or OTC orders.

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