Skip to main content
Glama
weex-mcp

weex-mcp

by weex-labs

Get futures positions

account_get_positions
Read-onlyIdempotent

Retrieve WEEX futures positions using request-level credentials, with optional symbol filtering and live or demo trading mode selection.

Instructions

Get futures positions using a request-level credential context.

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>",
      "trading_mode": "<trading_mode>",
      "credential": "<credential>"
    },
    "name": "account_get_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketYesWEEX market family: spot or futures.
symbolNoInstrument symbol in the WEEX catalog, for example BTCUSDT.
credentialYesRequest-scoped WEEX credential. The default runtime path is plaintext; credential_ref and encrypted_envelope require a custom host resolver.
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered. The description adds only the phrase 'using a request-level credential context', which hints that credentials are supplied per-call rather than pre-bound. It says nothing about rate limits, empty-result behavior, or whether positions are filtered by trading_mode.

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 padding. The brevity is efficient but leaves little structure, no clauses about scope or filtering.

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?

With rich annotations, a full output schema, and 100% schema coverage, the definition only needs to add scope behavior. It omits whether omitting symbol returns all positions, how trading_mode affects the result set, and what an empty position list implies, which is the remaining gap for a read tool of this complexity.

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 the enum explanations for market and trading_mode and the credential envelope details, so the schema carries the parameter semantics fully. The description adds no extra meaning about symbol scoping or credential variants beyond what is already documented.

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 and resource ('Get futures positions'), which distinguishes it from siblings like account_get_balance or account_get_orders. It does not explicitly contrast with any sibling, keeping it below a 5.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives. It never says whether symbol is optional-but-filtering, nor how this differs from account_get_orders or account_get_symbol_config.

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