Binance MCP Server

连通性测试

market_ping

Read-only

Tests connectivity to Binance exchange REST API. Requires no parameters; returns { ok: true } when successful.

Instructions

测试与币安交易所 REST API 的连通性。无需参数，成功返回 { ok: true }。

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_ping"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`ok`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv3.0.1Aug 23, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "ok": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

Addedv2.0.3Jun 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already indicate read-only and open-world behavior, and the description reinforces that by stating the tool only tests connectivity and returns a simple success object. It also discloses the expected success response, which adds value beyond the annotations. It does not describe failure behavior, but that is a minor omission for a ping tool.

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 a single concise sentence that front-loads the purpose, mentions the lack of parameters, and states the expected return value. Every word adds information, with no redundancy or filler.

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 simple no-parameter connectivity test with an output schema and readOnly annotations, the description provides all necessary information: what it tests, that no parameters are needed, and what a successful result looks like. Nothing required for an agent to select and invoke this tool is missing.

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?

There are zero parameters, and the description explicitly states 'no parameters required,' which removes any ambiguity. The baseline for zero parameters is 4, and the description fully confirms this without needing extra param details.

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 a specific action (testing connectivity) and a specific resource (Binance exchange REST API), and clearly differentiates itself from sibling market data tools by focusing on connectivity rather than data retrieval. It is not a tautology and adds detail beyond the tool name.

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 clearly conveys that this tool is used for a connectivity check and explicitly notes that no parameters are required. It does not name alternative tools or specify when not to use it, so it falls short of the 'explicit when/when-not' bar, but the use case is obvious and unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server