Skip to main content
Glama
weex-mcp

weex-mcp

by weex-labs

Get account trades

account_get_trades
Read-onlyIdempotent

Retrieve WEEX account trade fills for spot or futures in live or demo mode using request-scoped credentials and optional symbol, time, or order filters.

Instructions

Get user trade fills using a request-level credential context.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of records requested, encoded as a decimal string.
marketYesWEEX market family: spot or futures.
symbolNoInstrument symbol in the WEEX catalog, for example BTCUSDT.
end_timeNoInclusive end timestamp in Unix milliseconds.
order_idNoWEEX order identifier.
credentialYesRequest-scoped WEEX credential. The default runtime path is plaintext; credential_ref and encrypted_envelope require a custom host resolver.
start_timeNoInclusive start timestamp in Unix milliseconds.
trading_modeYesAccount or trading environment: live or demo.

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.1/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, so the safety profile is covered. Beyond that the description adds almost nothing: it does not mention that futures requires a start/end pair within a 7-day window, that spot requires a symbol, that limit caps differ by market (100 vs 2147483647), or how pagination works — all operationally significant for calling this correctly.

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 short sentence with no filler and the core purpose front-loaded. It is economical, though the economy shades into under-specification rather than efficiency.

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

Completeness4/5

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

An output schema exists so return values are covered, and it is a read-only, idempotent tool per annotations. But for a schema this complex — an eight-parameter oneOf branching between spot (symbol-based) and futures (time-range-based, capped at seven days) — the description should explain the branch conditions and limit caps, which it omits entirely.

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%, so every parameter including the nested credential envelope is documented in the schema itself. The description's single phrase, "request-level credential context," restates what the credential property already explains and adds no meaning to the other seven parameters.

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?

"Get user trade fills" names a specific verb and resource, and "user" distinguishes it from public market trade data such as market_get_recent_trades. However, it does not differentiate itself from other account-level reads like account_get_bills or account_get_orders, which could plausibly return overlapping fill data.

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 offers no when-to-use guidance, no exclusions, and no mention of alternatives. An agent must infer from the name alone that this is for fills rather than orders, bills, or market trades, and gets no help choosing between spot and futures modes.

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