Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_open_orders

Retrieves open custodial trade orders, optionally filtered by symbol to avoid slow all-pair scans. Requires a custodial solution API key.

Instructions

Get all open custodial trade orders.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

⚠️ Do not call without a symbol parameter as it returns all pairs and can be slow.

Response is an array of open orders with: symbol, orderId, price, origQty, executedQty, status, type, side, stopPrice, 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>"
    },
    "name": "binance_us_cust_open_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.
symbolNoTrading pair (e.g., BTCUSD). Recommended to always specify.

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

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses the authentication requirement, the performance penalty of omitting symbol, and enumerates the returned fields. Gaps remain around rate limits and result-set size/pagination behavior.

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?

Purpose is front-loaded, followed by the auth warning, the symbol caution, and the response shape — a sensible priority order. The response-field enumeration is slightly long but earns its place since there is no output schema.

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 two-parameter read tool with no annotations and no output schema, the definition covers purpose, auth, performance risk, and return fields. Only secondary details such as rate limits or ordering of results are absent, which is minor at this complexity.

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 coverage is 100%, so a baseline of 3 applies, but the description adds real meaning beyond the schema by explaining the consequence of omitting symbol ('returns all pairs and can be slow') where the schema only says 'Recommended'. It adds nothing extra about the rail parameter beyond the schema's uppercase example.

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 opens with a specific verb+resource ('Get all open custodial trade orders') and the word 'custodial' implicitly separates it from the non-custodial sibling binance_us_open_orders. It does not explicitly name that sibling as the alternative, which keeps it short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives two concrete preconditions: a custodial solution API key is required, and a symbol should always be supplied to avoid a slow all-pairs scan. It states conditions clearly but does not route the agent to a named alternative tool for non-custodial or filtered queries.

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