Skip to main content
Glama
weex-mcp

weex-mcp

by weex-labs

Get symbol price

market_get_symbol_price
Read-onlyIdempotent

Fetch the current WEEX spot or futures symbol price, optionally selecting INDEX or MARK for futures. Public endpoint; no credentials required.

Instructions

Get a WEEX market symbol price. Public endpoint; no credential required.

Input Schema

NameRequiredDescriptionDefault
marketYesWEEX market family: spot or futures.
symbolYesInstrument symbol in the WEEX catalog, for example BTCUSDT.
price_typeNoFutures price source: INDEX or MARK.

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?

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully carried by structured data. The description adds one genuinely new behavioral fact — that it is a public, credential-free endpoint — but says nothing about rate limits, price freshness, or whether the returned price is a last-trade, index, or mark value.

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

Conciseness5/5

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

Two short sentences with zero filler, and the core purpose is front-loaded before the auth note. Nothing is restated unnecessarily and no sentence fails to earn its place.

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 present, the description need not explain return values, and the annotations cover the safety profile, so this is close to sufficient for a simple read. However, given a crowded sibling set of price-adjacent tools, the definition leaves the agent without enough to know what this price represents or why to pick it over market_get_ticker_24h.

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% and the schema itself encodes the spot/futures conditional via oneOf, const, and the INDEX/MARK enum, so the parameters are fully self-documenting. The description adds no meaning beyond the schema — it never mentions market, symbol, or price_type — which meets the baseline for high-coverage schemas but nothing more.

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 ("Get a WEEX market symbol price") and names the market family, so the agent knows this returns a single symbol's price rather than a list. It does not distinguish itself from close siblings such as market_get_ticker_24h, market_get_book_ticker, or market_get_advanced_klines, so an agent cannot tell from the description which of these returns the same or a different price view.

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?

The only guidance is "Public endpoint; no credential required", which tells the agent this is callable without auth but not when to prefer it over the ticker, book-ticker, or kline siblings. Usage is implied by the tool name rather than stated, and no exclusions or alternatives are named.

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