Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_open_orders

Retrieve all open orders on Binance.US, optionally filtering by trading pair symbol to reduce rate-limit weight when checking active spot orders.

Instructions

Get all open orders on Binance.US. Can be filtered by symbol. Warning: Querying without symbol is heavier on rate limits (weight 40 vs 3).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "binance_us_open_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoTrading pair symbol to filter by (e.g., BTCUSD). If omitted, returns all open orders.
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

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose a valuable non-obvious trait — request weight 40 unfiltered vs. 3 filtered — which is behavior beyond anything in the schema. It omits authentication requirements, whether results are paginated/capped, and how much data an unfiltered call returns, leaving notable gaps for a zero-annotation tool.

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?

Three short sentences, front-loaded with the purpose and ending with the warning. 'Can be filtered by symbol' is slightly redundant with a self-documenting parameter, but nothing is padded or buried.

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 simple read-only list tool with a fully documented 2-parameter schema and no output schema, the definition covers purpose, filtering, and cost. It still leaves the agent guessing about return shape, result limits, and auth, which matters because there are no annotations to fill those gaps.

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 already 100%, so the baseline is 3. The description earns above baseline by attaching a concrete consequence to omitting 'symbol' (heavier rate-limit weight and broader result set), which the schema's own text only hints at.

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 open orders on Binance.US') plus a scope modifier (filterable by symbol). An agent can distinguish it from order-mutation siblings like binance_us_cancel_order, though it doesn't explicitly contrast with binance_us_all_orders (which presumably includes closed/historical orders).

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?

Explains the two usage modes (with vs. without symbol) and attaches a cost warning to the unfiltered mode, which is real guidance. However, it never names or routes to an alternative tool for historical/filled orders, so an agent must infer when this is the right call versus order-history siblings.

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