Skip to main content
Glama
Sign In
Binance MCP Server

Binance MCP Server

by iuk-ink
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

订单查询

trading_get_order
Read-onlyIdempotent

Retrieve details of a specific Binance futures order by providing either its orderId or origClientOrderId.

Instructions

返回：指定订单详情。orderId 与 origClientOrderId 二选一。

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

Input Schema

NameRequiredDescriptionDefault
symbolYes
orderIdNo
origClientOrderIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / orderId / description
      Removed value: -"系统订单ID"
    • removedInput schema / properties / origClientOrderId / description
      Removed value: -"自定义订单ID"
    • removedInput schema / properties / symbol / description
      Removed value: -"交易对符号 如 BTCUSDT"
  2. Addedv2.0.3

TDQS

B3.2/5.0
Behavior3/5

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

注解已提供readOnlyHint=true、openWorldHint=true、idempotentHint=true，安全形态已被覆盖。描述补充了“orderId与origClientOrderId二选一”这一约束，但对获取行为、错误、返回格式等没有额外披露。未与注解矛盾。

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

描述简洁紧凑，两句信息包含“返回结果”和“参数约束”，没有任何冗余内容。虽然可以更规范地改为一个完整句子，但在对效率和切题性上表现良好。

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?

对于工具的简单参数集合、该描述可一定程度上调用，但缺少“要查询的具体订单需要已知ID”这种应用场景提示，也没有提及返回值的形状或选型或许会因参数不同而异。它仍是“最小可用”而不算完整。

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?

模式描述覆盖率为0%，描述承担了部分参数解释：“orderId与origClientOrderId二选一”给出了两个参数的互斥选择关系，这对正确调用很关键。但未说明symbol参数、orderId的取值范围语义或origClientOrderId的格式，未完全弥补schema的空白。

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?

描述以明确的动词“返回”加资源“指定订单详情”表明这是按订单ID查询订单详情的工具。通过“指定订单”与“orderId/origClientOrderId”可以看出它与其他订单列表类工具（open_orders/order_history）区分，虽然未明确点名兄弟工具。

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?

描述没有说明何时使用此工具而不是trading_open_orders、trading_order_orders等替代方案。除“二选一”的参数约束外，没有给出明确的使用场景、前置条件或排除条件。

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