Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_otc_all_orders

Retrieve your Binance.US OTC trade order history and filter it by order ID, coin pair, or time range to review past over-the-counter trades.

Instructions

Query all OTC (Over-The-Counter) trade orders with optional filters.

Use this to retrieve your OTC trading history with various filtering options.

Response includes:

  • total: Total number of orders matching filters

  • rows: Array of order objects with full details

Each order contains: quoteId, orderId, orderStatus, fromCoin, fromAmount, toCoin, toAmount, ratio, inverseRatio, createTime

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (starts from 1)
limitNoRecords per page (default: 10, max: 100)
toCoinNoFilter by destination coin (e.g., USDT, SHIB)
endTimeNoEnd timestamp in milliseconds
orderIdNoFilter by specific order ID
fromCoinNoFilter by source coin (e.g., BTC, KSHIB)
startTimeNoStart timestamp in milliseconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
  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?

With no annotations at all, the description must carry the full behavioral burden. It does useful work by enumerating the return envelope (total, rows) and per-order fields, which compensates for the absent output schema. However, it never states that this is a read-only operation, nor mentions authentication requirements, rate limits, or whether page/limit are required for pagination.

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 in the first sentence, followed by usage and then the response shape. The field enumeration is longer than typical but earns its place because no output schema exists. Minor waste in the redundant second sentence restating the first.

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 seven-parameter, zero-annotation, no-output-schema tool, the description covers the two hardest gaps: what the response looks like and that filtering is optional. Missing are the read-only safety signal and any note on pagination semantics, but the schema already documents page/limit defaults and maxima.

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 one of the seven parameters (page, limit, coin filters, time range, orderId) is already documented with examples and defaults in the schema. The description adds no syntax, format, or interaction detail beyond that, so the baseline 3 applies.

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 and resource: "Query all OTC (Over-The-Counter) trade orders with optional filters," which is unambiguous about what the tool returns. It does not name a sibling (e.g. binance_us_otc_get_order for a single order) to draw the boundary, so it falls 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 Guidelines3/5

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

"Use this to retrieve your OTC trading history with various filtering options" implies the use case but gives no when-not conditions, no prerequisites, and no named alternative for a single-order lookup. The filtering angle is the only steer the agent gets.

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