Skip to main content
Glama
weex-mcp

weex-mcp

by weex-labs

Get advanced futures K-lines

market_get_advanced_klines
Read-onlyIdempotent

Retrieve futures historical, index-price, or mark-price K-lines by symbol and interval, with optional time ranges and record limits for market analysis.

Instructions

Get futures historical, index-price, or mark-price K-lines.

Input Schema

NameRequiredDescriptionDefault
kindYesTyped endpoint variant selected by this tool.
limitNoMaximum number of records requested, encoded as a decimal string.
marketYesWEEX market family: spot or futures.
symbolYesInstrument symbol in the WEEX catalog, for example BTCUSDT.
end_timeNoInclusive end timestamp in Unix milliseconds.
intervalYesK-line interval supported by the selected market.
price_typeNoFutures price source: INDEX or MARK.
start_timeNoInclusive start timestamp in Unix milliseconds.

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data. The shape follows the selected endpoint.
riskNo
auditNoRedacted request audit metadata, when applicable.
errorNo
summaryNo
expires_atNo
preview_idNo
request_idNo
user_confirmationNo
clarification_promptNo
clarification_requiredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds that the tool can return historical, index-price, or mark-price K-lines, but it says nothing about pagination, ordering, rate limits, or how the three variants behave differently.

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 a single efficient sentence with no filler and the operation is front-loaded. It is perhaps too sparse for a tool with eight parameters and a sibling named market_get_klines, but it is not verbose.

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?

With an output schema and full annotation coverage, the description need not explain return values or safety. However, for a complex, multi-variant K-line tool with a near-identical sibling, the definition is incomplete because it omits when to choose this tool over market_get_klines and how the 'advanced' behavior differs.

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?

Schema description coverage is 100%, so the schema already documents all eight parameters, including time ranges, limit, interval, and price_type. The description adds no parameter-specific meaning beyond restating the three price variants.

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 gives a specific verb and resource: it fetches futures historical, index-price, or mark-price K-lines. That is clear enough to understand the operation, but it does not distinguish this tool from the sibling market_get_klines, despite the 'advanced' name suggesting a meaningful difference.

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 names the three K-line variants but gives no guidance on when to use this tool instead of market_get_klines or what prerequisites apply. The agent is left to infer selection criteria entirely from the name and schema.

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