Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_recent_trades

Retrieve recent trades for a Binance.US trading pair, including trade ID, price, quantity, time, and maker/taker info. Use it to inspect market activity.

Instructions

Get recent trades for a trading pair on Binance.US. Returns trade ID, price, quantity, time, and maker/taker info.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of trades to return. Default 500, max 1000.
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.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully lists the returned fields (trade ID, price, quantity, time, maker/taker info), but it does not mention whether this is public market data, whether authentication is required, rate limits, or how recent the trades are.

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 tightly written sentences with the core action front-loaded and no wasted wording.

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 low-complexity market-data reader with two well-documented parameters and no output schema, the description is mostly complete. The main missing piece is routing guidance relative to sibling trade endpoints.

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 coverage is 100%, so both the symbol and limit parameters are already documented in the schema. The description mentions the trading pair but adds no syntax or usage detail beyond what the schema provides.

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 recent trades for a trading pair on Binance.US. It is clear what the tool does, though it does not explicitly distinguish itself from sibling trade tools such as agg_trades, historical_trades, or my_trades.

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?

The word "recent" implies a current-market-data use case, but there is no explicit guidance about when to use this tool instead of historical_trades, agg_trades, or my_trades, and no exclusions are stated.

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