Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_all_orders

Retrieve all orders (active, canceled, or filled) for a specific Binance.US trading pair to review complete order history and track order status.

Instructions

Get all orders (active, canceled, or filled) for a symbol on Binance.US. Returns order history.

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_all_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of orders to return (default 500, max 1000)
symbolYesTrading pair symbol (e.g., BTCUSD)
endTimeNoEnd time in milliseconds
orderIdNoOrder ID to start from. Gets orders >= this orderId.
startTimeNoStart time in milliseconds
recvWindowNoReceive window in milliseconds (max 60000)

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.2/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, and it only conveys that this is a read of order history. It says nothing about authentication needs, request weighting/rate limits, pagination behavior, or whether time-range parameters are required in practice.

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 sentences with the scope statement front-loaded and no filler. 'Returns order history' is close to redundant with 'Get all orders' but still cheaply confirms the return type, so it is efficient overall.

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 six-parameter, read-only history query with a fully specified input schema and no output schema, the description covers the essentials but omits pagination and time-window behavior that an agent would need to call it correctly. Adequate rather than complete.

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 every parameter including limit defaults, endTime/startTime in milliseconds, and the orderId 'gets orders >= this orderId' semantics is already documented. The description's mention of 'for a symbol' restates the schema and adds no new meaning.

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 ('Get all orders ... for a symbol on Binance.US') and scopes it to active, canceled, and filled statuses, so the agent can tell it is the general order-history reader rather than an open-orders-only call. It stops short of naming which sibling to use instead, so it does not fully differentiate.

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 parenthetical '(active, canceled, or filled)' implicitly signals this is the broad history query versus an open-orders tool, but the description never says when to prefer it over binance_us_open_orders or binance_us_cust_order_history, and lists no prerequisites or exclusions.

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