Skip to main content
Glama
Sign In
Binance MCP Server

Binance MCP Server

by iuk-ink
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

持仓查询

trading_positions
Read-onlyIdempotent

Get current trading positions from Binance futures. Specify a symbol to filter results, or omit to view all open positions.

Instructions

返回：当前持仓列表。缺省 symbol 返回全部持仓。

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

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and openWorldHints, so the core safety profile is covered. The description adds the default-omitted-symbol behavior, which is useful. It does not disclose whether '当前持仓' includes all accounts/markets, or how results are ordered/pagined.

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 two very short, front-loaded clauses with no filler. Every item conveys necessary behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool is simple and annotations cover side effects, so the scenario is low-complexity. But there is no output schema and no explanation of what fields each position entry includes (e.g. quantity, price, P/L), leaving the result shape somewhat ambiguous for the agent.

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 has no description on the sole symbol parameter, so the description's '缺省 symbol 返回全部' meaningfully supplies the key semantics: an omitted symbol returns all positions. For a single optional string param, that is the essential distinguishing guidance.

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?

Description states a clear verb ('返回') and resource ('当前持仓列表'), which immediately identifies it as a position-listing tool. It does not explicitly contrast with sibling tools like trading_balance or trading_position_mode, so it stops 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 provides no guidance on when to use this tool versus alternatives such as order history or balance queries. The '缺省 symbol 返回全部持仓' note is a parameter behavior, not a usage scenario or exclusion.

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