Skip to main content
Glama
trustxai

amazing-binance-mcp

by trustxai

binance_get_ticker_24h

Read-onlyIdempotent

Fetch 24-hour rolling price statistics for one or more symbols: price change, high, low, and volume. Supports single, multiple, or all symbols, with markdown or JSON output.

Instructions

Fetch 24-hour rolling price change statistics.

Calls GET /api/v3/ticker/24hr. Weight: symbol → 2; symbols → 2 for 1-20, 40 for 21-100, 80 for 101+; no symbol at all (all 3700+ symbols) → weight 80 — use sparingly.

When to Use:

  • For a market snapshot: price change %, high/low, volume over the last 24h.

When NOT to Use:

  • For a fixed calendar-day window — use binance_get_trading_day_ticker.

  • For a custom rolling window — use binance_get_rolling_ticker.

Returns: Markdown: up to 50 symbols as stat blocks. JSON: count/shown plus the tickers.

Examples: params = {"symbol": "BTCUSDT"} params = {"symbols": ["BTCUSDT", "ETHUSDT"], "type": "MINI"}

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

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses important runtime behavior: API weight costs for different symbol counts, a strong warning about the expensive all-symbols call, response format behavior, and a specific Binance error case. This is exactly the behavioral context an agent needs.

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 bold section headers, front-loads the critical weight warning, and includes only purposeful content: usage guidance, examples, return format, and error handling. Every sentence earns its place.

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?

The description is complete for a read-only market data tool: it covers selection criteria, alternatives, API endpoint, weight limits, return format, examples, and error behavior. Nothing essential is missing for an agent to call this tool correctly.

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

Parameters4/5

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

Schema description coverage is 0% at the top level, so the description must compensate. It provides concrete usage examples for `symbol`, `symbols`, and `type`, and maps `response_format` to Markdown/JSON in the Returns section. However, `symbol_status` is not addressed in the description, though the schema itself documents it.

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 the operation: fetching 24-hour rolling price change statistics via `GET /api/v3/ticker/24hr`. It explicitly distinguishes itself from sibling ticker tools in the When NOT to Use section, so an agent can select it without ambiguity.

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?

The description provides explicit When to Use and When NOT to Use sections, naming concrete alternatives (`binance_get_trading_day_ticker`, `binance_get_rolling_ticker`) for different time-window needs. This gives the agent clear selection criteria beyond general market snapshot use.

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