Skip to main content
Glama

wallet status

wallet-status
Read-onlyIdempotent

Is deposit/withdraw of a coin open right now, per network on bitget, gate, htx, kucoin + last-30-day notices from bitget, kucoin, okx (suspend/delist/migration) -> OPEN/PARTIAL/CAUTION Price: $0.02 per call, USDC on Base via x402.

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": {
      "coin": "<coin>"
    },
    "name": "wallet-status"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesstring, e.g. ARB
chainNooptional, e.g. ARB|ETH|TRC20
venuesNooptional list of bitget, gate, htx, kucoin

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, and the description adds real behavioral value beyond them: per-call pricing ($0.02 USDC on Base via x402), the returned classification set (OPEN/PARTIAL/CAUTION), the 30-day notice window, and the fact that venue coverage is partial across two different source lists. It does not spell out payment/auth mechanics or failure behavior, but that is a modest gap against a strong baseline.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense, front-loaded sentence with arrow notation for the return values; every clause (venues, notice window, notice types, output classes, price) contributes information. Nothing is padded or redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read-only lookup with full schema coverage and no output schema, the description supplies the key missing piece the agent would otherwise lack: the possible return classifications and how the two data sources (live status vs. 30-day notices) combine. Only the shape of the notice payload and behavior when a coin or venue is unknown remain unstated.

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 coverage is 100% with inline examples for every parameter, so the schema carries the load. The description reinforces the venue set (bitget, gate, htx, kucoin) and that results are per network, but adds no new syntax, defaults, or constraints such as what happens when venues is omitted.

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 names a specific question it answers (whether deposit/withdraw is open per network), the venues covered, and the supplementary notice data. This is clearly distinct from sibling names like wallet-risk or transfer-route in substance, though the definition never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the framing ('is ... open right now') rather than stated: an agent can infer you call this before attempting a transfer or bridging. There is no explicit when-not-to-use, no mention of which sibling to prefer for risk or routing decisions, and no note that the optional venues/chain params default to all venues.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources