Skip to main content
Glama
weex-mcp

weex-mcp

by weex-labs

Get account balance

account_get_balance
Read-onlyIdempotent

Retrieve WEEX spot or futures account balances for live or demo trading via request-scoped credentials.

Instructions

Get account balances using a request-level credential context.

Input Schema

NameRequiredDescriptionDefault
marketYesWEEX market family: spot or futures.
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.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The only added behavioral signal is "request-level credential context," which is vague and largely restates the credential field description in the schema, adding nothing about freshness, rate limits, or what an authenticated read exposes.

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 short sentence with the action front-loaded and no padding. The trailing credential clause is slightly jargon-heavy but not redundant enough to count as waste.

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 an output schema present, return values need not be described, and the nested credential object is fully specified in the schema. However, for a read whose result depends on which market and trading_mode are supplied, the description never explains what the balances represent, leaving it only minimally 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%, with market, trading_mode and credential all documented inline including enums and the plaintext/credential_ref/encrypted_envelope variants, so the baseline of 3 applies. The description does not clarify how market and trading_mode interact to select an account, which is the one semantic gap the schema leaves open.

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?

States a verb and resource ("Get account balances") that maps to the tool name, but adds no scope detail such as whether it returns spot, futures, or all balances, nor how it differs from siblings like account_get_positions or account_get_config. An agent can guess the purpose from the name, but the description itself contributes almost nothing beyond it.

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 or required permissions, and no routing to alternatives. The phrase "request-level credential context" hints at an invocation style but does not say when this tool should be chosen over other account_* reads.

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