Skip to main content
Glama
weex-mcp

weex-mcp

by weex-labs

Get futures funding rates

market_get_funding_rate
Read-onlyIdempotent

Retrieve current or historical futures funding rates to monitor funding costs and analyze market conditions.

Instructions

Get current or historical futures funding rates.

Input Schema

NameRequiredDescriptionDefault
modeYesOperation mode selected by this typed tool.
limitNoMaximum number of records requested, encoded as a decimal string.
marketYesWEEX market family: spot or futures.
symbolNoInstrument symbol in the WEEX catalog, for example BTCUSDT.
end_timeNoInclusive end timestamp in Unix milliseconds.
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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds nothing beyond that: no rate limits, no window constraints (the schema's 7-day max range goes unmentioned), no pagination or ordering behavior.

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

Conciseness3/5

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

A single front-loaded sentence with no padding, but it is terse to the point of carrying too little information for a six-parameter, two-mode tool. Efficient wording, insufficient content.

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?

The rich oneOf schema and an output schema relieve the description of explaining parameters and return values, so this is minimally viable. Still missing is the practical context an agent needs — the 7-day maximum range for history mode and the relationship between mode and symbol.

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 every parameter (mode, market, symbol, limit, start_time, end_time) is already documented in the schema. The description mentions current vs historical only at the level the mode enum already conveys, adding no format or constraint detail.

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?

States a specific verb and resource ('Get ... futures funding rates') and covers both current and historical variants. It is distinguishable from siblings like market_get_open_interest or market_get_klines by resource, though it never explicitly contrasts with them.

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?

Only implicit guidance via 'current or historical'; it never says when to pick each mode, that history requires a symbol, or that history ranges are capped. No alternatives or exclusions are named.

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