Skip to main content
Glama
weex-mcp

weex-mcp

by weex-labs

Get 24-hour ticker statistics

market_get_ticker_24h
Read-onlyIdempotent

Retrieve WEEX 24-hour ticker statistics for spot or futures markets by symbol to check price and volume changes.

Instructions

Get WEEX 24-hour ticker statistics.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "market": "<market>"
    },
    "name": "market_get_ticker_24h"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketYesWEEX market family: spot or futures.
symbolNoInstrument symbol in the WEEX catalog, for example BTCUSDT.

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 readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond them: no indication of which statistics are returned, no note on refresh cadence, rate limits, or behavior for unknown symbols. With annotations carrying the safety burden, this one-line restatement earns only a low score.

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?

A single front-loaded sentence with zero waste. It is efficient, though its brevity borders on under-specification rather than optimal sizing.

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?

An output schema exists so return values need not be described, and both parameters are documented in the schema. Still, for a market-data endpoint the definition leaves gaps around spot vs futures differences and error behavior when a symbol is invalid, making it only minimally complete.

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%, with both `market` (enum spot/futures) and `symbol` fully documented in the schema, so baseline 3 applies. The description adds no extra meaning such as symbol case sensitivity or whether symbol is optional for a whole-market summary.

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 ("Get") and resource ("WEEX 24-hour ticker statistics"), which is enough to separate it from siblings like market_get_symbol_price or market_get_book_ticker. It stops short of naming a sibling or explicitly contrasting scopes.

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?

There is no when-to-use guidance, no mention of when to prefer market_get_symbol_price or market_get_book_ticker instead, and no note on spot vs futures applicability. The agent must infer selection from the tool name alone.

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