Binance MCP Server

K 线历史

market_klines

Read-only

Retrieve candlestick (OHLCV) data for any Binance futures symbol and interval, with optional start and end time filters to analyze price movements within a specified period.

Instructions

获取指定交易对与周期的 K 线（含 OHLCV 与成交信息），支持时间范围过滤。

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>",
      "interval": "<interval>"
    },
    "name": "market_klines"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`symbol`	Yes
`endTime`	No
`interval`	Yes
`startTime`	No

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 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"

addedInput schema / properties / endTime

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

removedInput schema / properties / interval / description
```
Removed value: -"K 线周期"
```
changedInput schema / properties / limit / default
```
Previous value: -500New value: +100
```
removedInput schema / properties / limit / description
```
Removed value: -"数据量限制"
```

addedInput schema / properties / startTime

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

removedInput schema / properties / symbol / description
```
Removed value: -"交易对符号 如 BTCUSDT"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "close": {
+            "type": "number"
+          },
+          "closeTime": {
+            "type": "number"
+          },
+          "high": {
+            "type": "number"
+          },
+          "low": {
+            "type": "number"
+          },
+          "open": {
+            "type": "number"
+          },
+          "openTime": {
+            "type": "number"
+          },
+          "quoteVolume": {
+            "type": "number"
+          },
+          "takerBuyVolume": {
+            "type": "number"
+          },
+          "takerQuoteVolume": {
+            "type": "number"
+          },
+          "trades": {
+            "type": "number"
+          },
+          "volume": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "openTime",
+          "open",
+          "high",
+          "low",
+          "close",
+          "volume",
+          "closeTime",
+          "quoteVolume",
+          "trades",
+          "takerBuyVolume",
+          "takerQuoteVolume"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

Addedv2.0.3Jun 3, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds context about the return content (OHLCV and trade info) and time-range support, but does not disclose pagination, ordering, or any other parser-specific behavior. Acceptable but not rich.

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 in Chinese that front-loads the main operation ('获取指定交易器与周期的 K 线') and adds useful detail (OHLCV, volume, time range). Every part contributes value; there is no haffle.

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?

The tool is a simple read-only data retrieval operation, and annotations already cover its read-only nature. The description states the object, key parameters, and time-range filtering; with an output schema present, it does not need to explain return structure. Minor absence of limit/> pagination and clear sibling distinction leaves it 1 point short of complete.

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

Parameters3/5

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

With schema coverage at 0%, the description carries most param burden. It clarifies that `symbol` means trading pair and `interval` means period, and that `startTime`/`endTime` form a range filter. However, `limit` is never mentioned, and the schema has no per-parameter descriptions, so some parameter semantics still rely on type names/defaults.

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 verb '获取' and the resource 'K线' with specific scope (trading pair and cycle) and content (OHLCV plus volume/trade info). It does not explicitly distinguish itself from the sibling `market_continuous_klines`, so it falls short of a 5.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives like `market_continuous_klines` or `market_price`. It only mentions an available feature (time-range filtering), without stating prerequisites, exclusions, or alternative conditions.

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

Deploy Server