Skip to main content
Glama
weex-mcp

weex-mcp

by weex-labs

Get account bills

account_get_bills
Read-onlyIdempotent

Retrieves WEEX account bill and income records with request-scoped credentials, supporting spot or futures filtering by bill type, asset, symbol, and time range.

Instructions

Get account bill/income records using a request-level credential context.

Input Schema

NameRequiredDescriptionDefault
pageNoEndpoint-specific page number, encoded as a decimal string.
assetNoAsset or coin filter used by the selected account endpoint.
limitNoMaximum number of records requested, encoded as a decimal string.
monthNoSpot tax month in YYYY-MM format.
marketYesWEEX market family: spot or futures.
symbolNoInstrument symbol in the WEEX catalog, for example BTCUSDT.
coin_idNoSpot bill coin identifier, encoded as a decimal string.
biz_typeNoSpot bill business type filter.
end_timeNoInclusive end timestamp in Unix milliseconds.
bill_typeNoBill endpoint family: account, funding, tax, or income.
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.
income_typeNoFutures income type filter.
next_key_idNoFutures income pagination cursor identifier.
trading_modeYesAccount or trading environment: live or demo.
next_key_timeNoFutures income pagination cursor timestamp.

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

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

Annotations already disclose readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true. The description adds that access uses a request-level credential context, which is useful behavioral information, but it does not explain credential variants, pagination behavior, or the different market/trading-mode branches.

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 definition is a single front-loaded sentence with no filler. The phrase 'using a request-level credential context' is somewhat jargon-heavy but still compact and relevant to invocation.

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?

This is a highly complex tool with 16 parameters, nested oneOf branches, multiple bill families, and market-specific behavior. One sentence does not orient the agent to how bill_type interacts with the credential, market, trading_mode, or pagination parameters, even though the output schema and input schema provide structured detail.

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%, so the schema already explains all 16 parameters, including bill_type, market, trading_mode, credential, and pagination fields. The description adds almost no parameter-specific meaning beyond the phrase 'bill/income records,' leaving the baseline score appropriate.

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 description gives a verb, 'Get,' and a resource, 'account bill/income records,' but the resource is broad and does not distinguish among the four bill families (account, funding, tax, income) exposed by the schema. It also does not differentiate this tool from siblings such as account_get_transfer_records or account_get_trades.

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 exclusions, and no named alternative. An agent must infer from the schema that bill_type selects among account, funding, tax, and income record sets, and must infer when this tool is preferable to sibling record-listing tools.

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