Skip to main content
Glama
weex-mcp

weex-mcp

by weex-labs

Get futures conditional orders

account_get_conditional_orders
Read-onlyIdempotent

Retrieve open or historical futures conditional orders for a WEEX account, filtered by symbol and time range, to monitor pending triggers and review past outcomes.

Instructions

Get open or historical futures conditional orders.

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.
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

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds nothing beyond those annotations and the schema's own status enum — no mention of pagination behavior, the 90-day time-range cap, or credential requirements for this authenticated endpoint.

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?

The single sentence is front-loaded and free of filler, so every word earns its place. Brevity is appropriate structurally, though it leaves the description undersized for a nine-parameter tool with a nested credential object.

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?

For a tool with nine parameters, required credential, oneOf status branches, and a time-range bound encoded only in schema extensions, one sentence is not enough. An agent must infer how this differs from account_get_orders and how the open/history branches affect pagination and time filters.

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%, including detailed descriptions for limit, page, symbol, status, and the nested credential object, so the baseline is 3. The description contributes no additional parameter meaning (for example, symbol filtering or trading_mode semantics) beyond what the schema already provides.

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?

The sentence names the verb (Get) and resource (futures conditional orders) and adds a scope hint (open or historical). However, it essentially restates the tool name and title, and it never explains what a 'conditional order' is or how it differs from the ordinary orders returned by account_get_orders.

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 guidance on when to choose this tool over account_get_orders or any other sibling. 'Open or historical' hints at the status modes already documented in the schema, but no condition, prerequisite, or alternative is stated.

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