Skip to main content
Glama
Sign In
Binance MCP Server

Binance MCP Server

by iuk-ink
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

24h 行情统计

market_24hr_ticker
Read-only

Retrieve 24-hour rolling ticker data for a symbol or all markets, including price change, high/low, and volume. Use with a specific symbol to avoid heavy full-market requests.

Instructions

获取 24h 滚动统计（涨跌幅/高低价/成交量额）。缺省 symbol 返回全市场（weight 高，慎用）。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "market_24hr_ticker"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / symbol / description
      Removed value: -"交易对符号（不传则全部）"
  2. Addedv2.0.3

TDQS

A4.4/5.0
Behavior4/5

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

annotations 已声明 readOnlyHint 和 openWorldHint，描述在此基础上补充了全市场调用成本高的风险提示，对 agent 实际调用有实质价值。未提限频、返回体量等，但已有注解覆盖安全性，这仍高于基本要求。

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?

整个描述一句话完成，主行为在前，调用警告在后，没有重复 schema 结构字段。每个词都有信息量，属于简洁且高密度的工具说明。

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?

对单参数、有安全注解、无输出 schema 的工具来说，已交代用途、返回维度、缺省行为和高成本风险。缺少数显式替代条件与 symbol 格式示例，但对于这类简单只读行情工具已达到足够完整度。

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 仅有一个可选的 symbol，且描述覆盖率为 0；描述明确说明缺省 symbol 时的语义是会返回全市场并带来高 weight，这超出 schema 本身的信息。虽然没有给出 symbol 写法示例，但 symbol 为自明性参数，可选行为已经落实清楚。

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?

描述以具体动词“获取”指明行为，“24h 滚动统计（涨跌幅/高低价/成交量额）”明确资源类别，并与 market_price、market_book_ticker 这类实时快照工具区分。缺省 symbol 返回全市场这一行为也进一步明确了工具边界。

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

Usage Guidelines4/5

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

描述了缺省 symbol 时返回全市场，并明确提示 weight 高、慎用，这是清晰的调用条件。虽然没有显式列举可替代工具，但已提供了决定“带 symbol 还是不带”的直接指导。

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