Skip to main content
Glama
weex-mcp

weex-mcp

by weex-labs

Get candlestick data

market_get_klines
Read-onlyIdempotent

Fetch WEEX spot or futures candlestick data by symbol and interval to analyze price movements; public endpoint, no credentials required.

Instructions

Get WEEX candlestick/K-line data. Public endpoint; no credential required.

Input Schema

NameRequiredDescriptionDefault
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.
intervalYesK-line interval supported by the selected market.

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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new context that annotations don't carry: that this is a public endpoint requiring no credentials. It stops short of mentioning rate limits, pagination/limit semantics, or that spot does not accept a limit parameter.

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?

Two short sentences with no filler; the resource is front-loaded and the auth caveat follows immediately. It is efficient but arguably undersized for a tool whose schema has a oneOf split between spot and futures calling conventions.

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

Completeness4/5

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

An output schema exists, the input schema is fully described, and annotations cover safety, so the description needn't restate return values or read-only behavior. It covers the one thing structured fields don't (no credentials needed); the main remaining gap is routing guidance versus the advanced-klines sibling.

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%, including enum values for market and interval and a documented string-integer limit with a 1-1000 range, so the baseline is 3. The description adds no meaning beyond the schema for any of the four parameters.

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 WEEX candlestick/K-line data), which an agent can match to a charting or OHLC request without opening the schema. It does not distinguish itself from the sibling market_get_advanced_klines, so an agent cannot tell from the description alone which of the two to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the purpose; there is no explicit 'use this when' or exclusion against market_get_advanced_klines or the ticker/price tools. The 'Public endpoint; no credential required' clause does give a usable prerequisite (callable without auth), which raises it above pure no-guidance.

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