Skip to main content
Glama
weex-mcp

weex-mcp

by weex-labs

Get recent public trades

market_get_recent_trades
Read-onlyIdempotent

Fetch recent public WEEX trades for a spot or futures symbol to inspect recent market activity. Provide market and symbol, and optionally set a result limit.

Instructions

Get recent public WEEX trades.

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

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

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety and mutability are fully covered without the description. The description adds essentially no behavioral context beyond that: nothing about ordering of returned trades, whether data is live or cached, or any rate limits on this public endpoint.

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

Conciseness3/5

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

The single sentence is front-loaded and free of padding, which is good. But its brevity comes at the cost of under-specification rather than genuine economy, so it earns a middle score rather than a top one.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema and rich annotations carry much of the burden, so the description need not explain return values. Still, for a tool whose entire semantics hinge on "recent," the definition leaves the ordering and freshness of results undefined, and gives no hint about the practical effect of the limit parameter.

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 each parameter (market enum, symbol, limit with its 1-1000 range) is documented in the schema itself, so the baseline of 3 applies. The description contributes nothing extra, such as what limit defaults to or how the market/symbol pair constrains valid requests.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get recent public WEEX trades" names a verb and resource, so the basic action is clear, and "public" loosely signals it is not account-scoped like account_get_trades. However, it never explicitly contrasts itself with that sibling, so the agent must infer the distinction from the word "public" alone.

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 statement of prerequisites (e.g. whether authentication is needed for public market data), and no explicit routing to or away from account_get_trades. Only the single adjective "public" hints at the boundary, which is too implicit for reliable tool selection.

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