Skip to main content
Glama
Sign In
Binance MCP Server

Binance MCP Server

by iuk-ink
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

最优买卖报价

market_book_ticker
Read-only

Get best bid/ask price and quantity for a symbol or all markets, offering a lightweight alternative to full order book depth.

Instructions

获取最优买/卖价与数量（比订单簿轻量）。缺省 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_book_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.5/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already declared safe, the description adds real behavioral value by noting that omitting symbol changes the scope to the entire market and increases API weight. This is beyond both the schema and annotations and helps the agent avoid an expensive accidental call.

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?

Two parenthetical-clauses, each crucial: no inherited wasted. The core return value is front-loaded, the weight caveat at the end is essential. 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?

For a low-complexity light market data tool with no output schema, the description fully enough: what it returns, that it is lighter than the orderbook, and the scope/weight implication of the default. The agent can select and call it confidently without missing unknown consequences.

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 description coverage is 0%, but the description compensatesru: 'symbol' semantics by explaining that omitting symbol returns the whole market, and 'weight high, use with caution'. The only param is self-evidently a market ticker symbol, so absentity of format examples is a meaning gap but not a serious one.

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 states in Chinese that this retrieves the best bid/ask price and quantity, which is a specific verb + resource. It also explicitly distinguishes it from the order book by calling it lighter, making it easy to tell apart from market_orderbook and other market data tools.

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?

The description gives clear selection context: use it when you need top-of-book prices, and it contrasts with the full order book. It also warns that omitting symbol returns the whole market with a high weight, so an agent knows when to be cautious. It stops short of naming an explicit alternative tool, but the intended contrast to the order book is evident.

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