kvant-binance-mcp

futures_get_income

Retrieve futures income history from Binance using API key. Filter by symbol, income type, or time range.

Instructions

Get futures income history (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_get_income"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Number of records (default 100, max 1000)
`symbol`	No	Filter by symbol
`endTime`	No	End time in ms
`startTime`	No	Start time in ms
`incomeType`	No	Filter by income type

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 4, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It states 'requires API key' (authentication), but does not disclose whether the operation is read-only, has rate limits, or any side effects. The behavioral profile is largely opaque.

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

Conciseness2/5

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

The description is very short (one sentence), which achieves conciseness but at the cost of omitting important information about usage and behavior. It is under-specified relative to the tool's complexity and lack of annotations.

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

Completeness2/5

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

With no output schema and no annotations, the description fails to describe return values, pagination, or how to interpret the data. Given the tool has 5 optional parameters and no output schema, the description is incomplete for effective use.

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 input schema has 100% coverage with all 5 parameters described. The description adds no additional meaning beyond the schema. Baseline of 3 is appropriate since the schema already handles parameter documentation.

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 it retrieves futures income history. The verb 'Get' and resource 'futures income history' are specific. However, it does not explicitly distinguish this from sibling tools, such as futures_account_info or futures_balance, which also deal with financial data for futures.

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 only mentions that an API key is required, but does not provide guidance on when to use this tool versus alternatives, such as for historical income queries versus current account balances. No exclusion criteria or context for use are given.

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