Skip to main content
Glama
trustxai

amazing-binance-mcp

by trustxai

binance_get_recent_trades

Read-onlyIdempotent

Retrieve recent public trades for a symbol to view executed prices, quantities, and trade sides.

Instructions

Fetch the most recent public trades for a symbol.

Calls GET /api/v3/trades (weight 25). Always returns the latest trades — there is no way to page backward here (use binance_get_agg_trades with from_id for that).

When to Use:

  • To see the last executed prices/sizes and maker/taker mix for a symbol.

When NOT to Use:

  • To page through trade history by id — use binance_get_agg_trades.

  • For your OWN trades — use binance_get_my_trades (signed).

Returns: Markdown: a table of up to 100 trades (id, time, price, qty, side). JSON: the full requested page (up to limit), uncapped.

Examples: params = {"symbol": "BTCUSDT", "limit": 50}

Error Handling: An unknown symbol raises Binance -1121 Invalid symbol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds key behavioral details: the endpoint weight (25), the impossibility of backward paging, and the error message for invalid symbols. These go beyond the annotation hints and clarify operational constraints.

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 well-structured with clear sections, front-loaded purpose, and every sentence contributes value. It includes usage guidance, return format, examples, and error handling without redundancy.

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

Completeness5/5

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

Given the tool's complexity, the presence of an output schema, and rich sibling context, the description is complete. It covers what the tool does, when to use it, what it returns, and common errors, leaving no critical gap for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden. It explains the effect of response_format (markdown caps at 100 trades, JSON uncapped), gives a concrete example with limit=50, and clarifies that limit is up to 1000. This fully compensates for the missing schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Fetch the most recent public trades for a symbol' and explicitly contrasts with sibling tools (binance_get_agg_trades for paging, binance_get_my_trades for own trades), making the purpose unambiguous and distinct.

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

Usage Guidelines5/5

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

Provides explicit 'When to Use' and 'When NOT to Use' sections, naming alternatives and the conditions that select them. This leaves no ambiguity about when to invoke this tool versus others.

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