Skip to main content
Glama
weex-mcp

weex-mcp

by weex-labs

Get best bid and ask quotes

market_get_book_ticker
Read-onlyIdempotent

Retrieve WEEX best bid and ask quotes for a spot or futures symbol to check current market pricing.

Instructions

Get WEEX best bid and ask quotes.

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_book_ticker"
  }
}

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 readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds nothing beyond the title: it does not say what happens when symbol is omitted, whether quotes are per market family, or whether data is real-time versus delayed.

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 short sentence with the resource front-loaded and zero filler. It is efficient but borders on under-specification rather than well-structured completeness.

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?

A simple read-only tool with a full input schema, an output schema, and annotations covering safety, so much of the burden is lifted. Still, an agent gets no information on symbol omission behavior or data freshness, leaving gaps for a market-data call.

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 documented inline, so the schema carries parameter meaning. The description adds no additional semantics, which is the expected baseline when coverage is high.

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 resource – best bid and ask quotes – which is distinguishable from siblings like market_get_ticker_24h or market_get_symbol_price. The verb is generic ("Get") and it does not explicitly contrast itself with any alternative, so it falls short of a 5.

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?

No guidance on when to use this tool versus the many other market-data siblings (24h ticker, symbol price, depth). No prerequisites, no mention of whether symbol is optional to fetch all quotes, and no exclusions.

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