Skip to main content
Glama
weex-mcp

weex-mcp

by weex-labs

Get futures symbol configuration

account_get_symbol_config
Read-onlyIdempotent

Retrieves futures symbol configuration for a WEEX account, returning contract settings for a given instrument so you can verify trading parameters before placing orders.

Instructions

Get futures account symbol configuration.

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

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

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and open-world, so the safety profile is covered. The description adds nothing beyond that: it does not say whether an omitted optional 'symbol' returns configuration for all symbols or a default, nor whether the data is cached or fetched live from the exchange.

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, but its brevity is under-specification rather than efficiency for a tool with a nested credential union and an optional symbol parameter. There is no structure to speak of.

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 exists so return values need not be explained, and annotations cover safety, but the description still leaves key gaps: the meaning of the optional 'symbol', the live-only trading_mode constraint, and how this differs from account_get_config. For a tool with nested credential shapes this is thinner than adequate.

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 there are four documented parameters, so the schema itself carries the meaning; baseline 3 applies. The description contributes no additional semantics, notably missing the meaningful behavior that 'symbol' is optional despite being the resource being configured.

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

Purpose2/5

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

The description 'Get futures account symbol configuration' is essentially a restatement of the title 'Get futures symbol configuration' and the tool name, adding only the word 'account'. It gives no detail on what 'configuration' comprises (leverage caps, min/max order size, fee tiers, contract specs) and does not distinguish it from the sibling account_get_config.

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 mention of prerequisites (the credential is required), and no routing hint toward or away from sibling tools such as account_get_config, market_get_exchange_info, or market_get_catalog, which plausibly overlap with symbol metadata lookup.

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