Binance MCP Server

未平仓量

market_open_interest

Read-only

Get the current open interest for a specified trading pair to assess market participation and potential price movement.

Instructions

获取指定交易对当前未平仓量。

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

Input Schema

Name	Required	Description	Default
`symbol`	Yes

Output Schema

Name	Required	Description	Default
`time`	Yes
`symbol`	Yes
`openInterest`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

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": {
+    "openInterest": {
+      "type": "number"
+    },
+    "symbol": {
+      "type": "string"
+    },
+    "time": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "symbol",
+    "openInterest",
+    "time"
+  ],
+  "type": "object"
+}

Addedv2.0.3Jun 3, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already mark this as readOnlyHint=true, and the description adds that the result is 'current' and scoped to a pair. It does not mention freshness, rate limits, or behavior on invalid symbol, but for a read-only snapshot that gap is acceptable.

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?

One single sentence with no redundant words or filler. The important resource and scope are front-loaded.

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 read-only tool with an output schema and annotations covering safety, the description is nearly sufficient. The only remaining gap is the exact symbol format and possibly supported contract type, but those are minor for a simple 'get by symbol' tool.

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?

The schema supplies a bare 'symbol' string with no description and 0% schema description coverage. The description clarifies that symbol means '交易对', but it does not define the expected format, casing, or exchange convention, so the parameter semantics is only partially compensated.

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 uses a specific verb and object: it '获取' the '当前未平仓量' for a given trading pair. This clearly distinguishes the resource from market_price, market_funding_rate, and other sibling tools, but it does not explicitly name any sibling or contrast itself.

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?

Description does not explicitly provide when to use or when not to use this tool. The intended usage is inferred because the resource is open interest; however, with 50+ sibling tools in the market domain, no explicit guidance is given for selecting this one over a more general market tool.

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

Deploy Server