Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_historical_trades

Fetches older historical trades for a Binance.US trading pair, with optional trade ID and limit filters. Use it to retrieve past market data for analysis; requires a MARKET_DATA-enabled API key.

Instructions

Get older historical trades for a trading pair. Requires API key with MARKET_DATA permission.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of trades. Default 500, max 1000.
fromIdNoTrade ID to fetch from (inclusive).
symbolYesTrading pair symbol, e.g., BTCUSD

Schema Changelog

Changes observed during successful MCP inspections.

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

No annotations are supplied, so the description carries the full burden, and it does contribute one genuinely useful behavioral fact: an API key with MARKET_DATA permission is required. It says nothing about rate limits, result ordering, or how to page backwards through history, which are the main behavioral risks for a historical-trades endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste, with the operation front-loaded and the prerequisite second. Nothing could be removed without losing information.

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?

With no annotations and no output schema, the description should at minimum say what a returned trade looks like or that results are paginated by trade ID. It covers purpose and auth but leaves return shape and pagination semantics undocumented.

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%, with symbol, limit (default 500, max 1000) and fromId already documented in the schema. The description adds no meaning 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 states a specific verb and resource ('Get older historical trades') plus scope ('for a trading pair'), and the word 'older' implicitly separates it from recent-trade siblings. It stops short of naming binance_us_recent_trades or binance_us_agg_trades as the contrasting options, so differentiation is suggestive rather than explicit.

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?

Usage is only implied: 'older historical trades' signals this is the deep-history variant, but there is no statement of when to choose it over recent_trades or agg_trades, and no mention of the fromId pagination workflow that presumably drives repeated calls. An agent must infer the selection rule from the adjective alone.

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