Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_my_trades

Retrieve executed trade history for a specific Binance.US trading pair, including price, quantity, commission, and timestamps.

Instructions

Get trade history for a specific trading pair. Returns executed trades including price, quantity, commission, and timestamps.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of trades to return. Default: 500, Max: 1000
fromIdNoTrade ID to fetch from. Default gets most recent trades.
symbolYesTrading pair symbol, e.g., BTCUSD, ETHUSD
endTimeNoEnd time in milliseconds
orderIdNoFilter by order ID
startTimeNoStart time in milliseconds
recvWindowNoThe value cannot be greater than 60000

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

C2.9/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 disclosure burden. It reports which fields come back, which is useful, but omits that this is a private/signed endpoint scoped to the authenticated account's own fills, says nothing about rate limits or pagination, and does not explain how the time/id filters page through results.

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?

Two compact sentences with the operation stated first and the return shape second; nothing is wasted. The brevity is appropriate, though the second sentence partially restates what the name already implies.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter, account-private endpoint with no annotations and no output schema, the description is thin: it never states the auth requirement, the account scoping, or how the paging parameters behave. An agent could invoke it correctly on symbol alone but would likely misuse the time/fromId filters.

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 all seven parameters (symbol, limit, fromId, startTime, endTime, orderId, recvWindow) are already documented in the schema. The description adds no additional meaning, such as default window behavior or how fromId interacts with startTime, 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?

States a specific verb and resource ('Get trade history for a specific trading pair') and enumerates the returned fields, so the operation is unambiguous. However, it does not distinguish itself from close siblings such as binance_us_recent_trades, binance_us_historical_trades, and binance_us_agg_trades, which occupy nearly the same semantic space.

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 guidance, no exclusion criteria, and no mention of the sibling tools that fetch trade data with different scope or aggregation. The agent must infer from the name alone that this is the account-scoped trade list rather than an aggregate or public feed.

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