Skip to main content
Glama
weex-mcp

weex-mcp

by weex-labs

Get account orders

account_get_orders
Read-onlyIdempotent

Retrieve open, historical, or single spot and futures orders using request-level credentials to check order status and details.

Instructions

Get open, historical, or single order information using a request-level credential context.

Input Schema

NameRequiredDescriptionDefault
pageNoEndpoint-specific page number, encoded as a decimal string.
limitNoMaximum number of records requested, encoded as a decimal string.
marketYesWEEX market family: spot or futures.
statusYesOrder query mode: open, history, or single.
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.
client_order_idNoStable caller-supplied order identifier; maps to WEEX newClientOrderId for new orders.

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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The only added behavioral note is 'using a request-level credential context', which signals per-call authentication, but that same fact is already spelled out in the credential parameter's schema description.

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 front-loaded sentence with no filler, and the mode enumeration comes early. It is efficient, though it errs toward being too terse for an 11-parameter polymorphic tool.

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?

The tool is complex (oneOf branches across market/trading_mode/status, 11 params), but an output schema exists and schema coverage is complete, so the structural fields compensate. The description still omits the mode-specific requirements and the fact that history queries are time-bounded, leaving the agent to discover constraints from the schema.

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% across all 11 parameters, including enum values, patterns, and ranges, so the schema does the heavy lifting. The description adds no meaning beyond it — no mention of symbol scoping, time-range limits, or pagination behavior.

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?

The description names a specific verb and resource ('Get ... order information') and enumerates the three query modes (open, historical, single), which maps onto the status enum. It does not explicitly distinguish itself from siblings like account_get_conditional_orders or account_get_trades, so differentiation is left to inference.

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?

Mentioning the three modes implies the selection context, but the description never says when to pick open vs history vs single, nor any prerequisite such as providing order_id/client_order_id for single lookups. No alternative tool is named for adjacent needs (trades, conditional orders).

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