Skip to main content
Glama
Sign In
Binance MCP Server

Binance MCP Server

by Lubodi-Code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_24h_stats

Retrieve 24-hour trading statistics for any Binance symbol, including volume, price change percentage, and high/low prices.

Instructions

Estadisticas de 24h de un simbolo (volumen, cambio %, high/low). Ej: 'ETHUSDT'.

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": "get_24h_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It lists the returned fields (volume, change %, high/low) but omits response format, error behavior, and whether the 24h stats are rolling or daily.

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?

A single, focused sentence with a practical example. No filler or redundant information; every word contributes.

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 one-parameter stats tool, the description names the included metrics and provides an example. Without an output schema, it could describe the response shape or error cases, but the listed fields give adequate functional context.

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?

The schema provides only the parameter name 'symbol' with no description (0% coverage). The description compensates by explaining that the parameter is a trading symbol and gives a concrete example ('ETHUSDT'), clarifying the expected format.

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 clearly states the tool returns 24h statistics for a symbol, listing volume, change percentage, and high/low. This distinguishes it from siblings like get_price and get_klines, though it lacks an explicit verb.

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

Usage Guidelines3/5

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

The intended use is implied: fetch 24h market stats for a symbol. The example clarifies the symbol parameter, but no explicit guidance is given about when to prefer this over alternatives like get_price or get_klines.

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