Skip to main content
Glama
weex-mcp

weex-mcp

by weex-labs

Get order book depth

market_get_depth
Read-onlyIdempotent

Retrieve WEEX order book depth for spot or futures markets by symbol to inspect liquidity and price levels without credentials.

Instructions

Get WEEX order book depth. Public endpoint; no credential required.

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>",
      "symbol": "<symbol>"
    },
    "name": "market_get_depth"
  }
}

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.

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond them by stating this is a public endpoint requiring no credentials, but says nothing about rate limits, throttling, or whether depth is snapshotted versus streamed.

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 the resource stated first and the access constraint second; nothing is wasted. Its brevity is appropriate given the full schema and an output schema, though a single clause on depth semantics would have earned the fifth point.

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?

Output schema exists, so return values need not be explained, and all three parameters are documented in the schema. What remains thin is why an agent would pick this over the book-ticker sibling and what the returned depth levels represent.

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 self-documenting enum values for market and limit, so the schema carries parameter meaning. The description adds nothing about what the limit values 15 versus 200 imply for response size, leaving the baseline 3.

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?

Names a specific verb and resource: 'Get WEEX order book depth.' An agent can tell this is an order-book snapshot rather than a trade list or price ticker, though the description never contrasts it with the nearby market_get_book_ticker sibling.

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?

The description gives no when-to-use or when-not-to-use guidance and names no alternative for related market-data needs. The only routing aid is the 'public endpoint; no credential required' note, which implies it can be called without auth but does not help choose among siblings.

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