Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_order_book

Retrieve order book depth with bids and asks for a Binance.US trading pair, including price levels and quantities to assess market liquidity.

Instructions

Get order book depth (bids and asks) for a trading pair on Binance.US. Returns price levels with quantities. Weight varies based on limit (1-100: weight 1, 101-500: weight 5, 501-1000: weight 10, 1001-5000: weight 50).

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of price levels. Valid values: 5, 10, 20, 50, 100, 500, 1000, 5000. Default 100, max 5000.
symbolYesTrading pair symbol, e.g., BTCUSD

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.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose genuinely useful behavior beyond the schema: the return contains price levels with quantities, and request cost scales in tiers (weight 1/5/10/50 by limit range). It omits whether the endpoint is public/unauthenticated, error behavior, and the rest of the response shape (e.g., update ID), which is a meaningful gap for a tool with zero annotation coverage.

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 sentences, front-loaded with purpose followed by return content and cost tiers. The weight parenthetical is long but every clause is informative; nothing is padding.

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 two-parameter market-data tool with no output schema and no annotations, the description covers purpose, return gist, and rate-limit cost adequately, but leaves the full response structure and authentication requirements unstated.

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 the schema already documents both parameters including the valid limit values. The description adds value by mapping limit ranges to rate-limit weight, which the schema does not convey. It does not add further symbol-format detail beyond the schema 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 names a specific verb and resource ('Get order book depth (bids and asks) for a trading pair') and scopes it to Binance.US. An agent can distinguish this from ticker/avg-price siblings on the basis of the resource alone, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternatives are mentioned (e.g., when to prefer this over binance_us_ticker_book). Usage is only implied by the resource name.

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