kvant-binance-mcp

futures_open_orders

Retrieve your open futures orders with optional symbol filtering for targeted management.

Instructions

Get open futures orders (requires API key)

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

Input Schema

Name	Required	Description	Default
`symbol`	No	Filter by symbol (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 4, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Without annotations, the description carries the full burden. It fails to disclose whether this is a read operation (implied but not stated), what happens if no open orders exist, potential rate limits, or any side effects. The note about API key is minimal.

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?

The description is very short with two pieces of information (purpose and API key requirement). It is front-loaded and concise, though the parenthetical '(requires API key)' could be separated for clarity.

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?

For a simple read tool with one optional parameter and no output schema, the description is adequate but lacks context on return format or behavior when no orders match. Given sibling tools, more detail on 'open' status would improve completeness.

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?

There is one optional parameter 'symbol' with a schema description 'Filter by symbol (optional)'. The tool description adds no additional meaning beyond the schema, so baseline 3 applies given 100% schema coverage.

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 'Get' and the resource 'open futures orders', indicating a read operation on open orders. It distinguishes from sibling tools like 'futures_all_orders' and 'futures_new_order', though it could be more explicit about what 'open' means (e.g., unfilled or active orders).

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?

No guidance is provided on when to use this tool versus alternatives like 'futures_all_orders' (all orders) or 'futures_position_info'. The only usage note is 'requires API key', which is a prerequisite but not a usage guideline.

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