Skip to main content
Glama
weex-mcp

weex-mcp

by weex-labs

Get Spot transfer records

account_get_transfer_records
Read-onlyIdempotent

Retrieve read-only Spot account transfer history to review past transfers, filtered by timestamp, coin ID, or source account type.

Instructions

Get read-only Spot account transfer history.

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

Input Schema

NameRequiredDescriptionDefault
afterNoReturn records created after this Unix millisecond timestamp.
limitNoMaximum number of records requested, encoded as a decimal string.
beforeNoReturn records created before this Unix millisecond timestamp.
marketYesWEEX market family: spot or futures.
coin_idNoSpot bill coin identifier, encoded as a decimal string.
from_typeNoSource account type filter for Spot transfer records.
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.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so restating 'read-only' adds no new information. The description says nothing about pagination via limit/before/after, filtering behavior, rate limits, or which credential modes work at runtime — all real behavioral concerns with annotations covering only the safety profile.

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?

It is a single sentence with no wasted words and is front-loaded, which is good. But the brevity crosses into under-specification: the one clause it contains ('read-only') duplicates the annotations rather than carrying useful content.

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 an 8-parameter tool with a nested, three-variant credential object, two enums, and an output schema, a six-word description is far too thin. Even with the output schema covering return values, the agent gets no help on transfer-type semantics or credential mode requirements.

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 every parameter is already documented in the schema, and a baseline of 3 applies. The description adds nothing about from_type values, coin_id usage, or how before/after interact, so it does not exceed the baseline.

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?

The description states a specific verb and resource: 'Get ... Spot account transfer history.' The word 'transfer' plus 'Spot' narrows it ahead of siblings like account_get_bills or account_get_trades, but it never explicitly contrasts itself with them, so an agent must still infer the boundary.

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 exclusion, and no mention of the closest alternatives (account_get_bills, account_get_trades) or prerequisites. The agent is left to guess from the name alone whether this is the right tool for account movement history.

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