Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_agg_trades

Retrieve compressed aggregate trades for a Binance.US trading pair, grouping trades with matching time, order, and price into single records for cleaner market data.

Instructions

Get compressed aggregate trades. Trades with same time, order, and price are aggregated.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of trades. Default 500, max 1000.
fromIdNoAgg trade ID to start from.
symbolYesTrading pair symbol, e.g., BTCUSD
endTimeNoEnd time in ms.
startTimeNoStart time in ms.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / endTime / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / fromId / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / startTime / maximum
      Added value: +9007199254740991
  2. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It explains the aggregation rule but does not disclose access requirements, rate limits, pagination behavior, or return format.

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?

The description is two short sentences with no unnecessary wording. The core purpose and aggregation behavior are front-loaded.

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?

The schema fully documents the five parameters, and the aggregation rule is explained. However, the description omits usage context relative to sibling trade endpoints and does not describe the response shape, leaving meaningful gaps for an agent selecting the tool.

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 each parameter documented in the input schema. The description adds no parameter-specific semantics beyond that, so the baseline score of 3 is appropriate.

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 compressed aggregate trades') and explains the aggregation rule. It does not distinguish this from sibling tools such as binance_us_recent_trades or binance_us_historical_trades, so full sibling differentiation is missing.

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?

Provides no explicit guidance on when to use this tool versus recent or historical trade endpoints. The intended use as aggregated market data can be inferred, but there are no stated conditions or exclusions.

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