Skip to main content
Glama
weex-mcp

weex-mcp

by weex-labs

Get WEEX market catalogs

market_get_catalog
Read-onlyIdempotent

Retrieve WEEX spot or futures coin metadata and API-tradable symbol catalogs to identify available assets and markets for trading or data integration.

Instructions

Get WEEX coin metadata or API-tradable symbol catalogs.

Input Schema

NameRequiredDescriptionDefault
marketYesWEEX market family: spot or futures.
catalogYesCatalog family to return: coins or API-tradable symbols.

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
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so safety is covered elsewhere. The description adds no behavior of its own: no mention of result size, pagination, caching freshness, or that results are catalog snapshots. It essentially restates the title.

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?

One front-loaded sentence with no padding or redundancy. It is efficient, though its brevity leaves useful context out rather than being genuinely optimal.

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 and both params are documented, so the core contract is covered. However, the description does not explain the practical purpose of the catalogs or the market/catalog compatibility, leaving the agent to infer intent for an open-world read tool.

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 parameters enum-documented, so the baseline is 3. The description adds no meaning beyond the schema, and notably does not restate the constraint that futures supports only 'symbols' — though the oneOf enforces it.

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 coin metadata or API-tradable symbol catalogs'), which is enough to separate it from sibling market-data tools like klines, depth, and tickers. It stops short of saying what the catalogs are used for or how they differ from market_get_exchange_info.

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?

Implied usage only: an agent can infer this is a reference-lookup tool, but the description never says when to call it (e.g., to resolve symbols before placing orders or querying other market tools) or when another tool is preferable. 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.