Skip to main content
Glama

Crypto Support Desk (zh/en)

Pre-send address check (free)

check_crypto_address
Read-onlyIdempotent

FREE, offline. Before a user sends or a support agent confirms a deposit address: detects the address family (EVM, TRON, Bitcoin, Solana, TON, XRP, ...), validates checksum and format, cross-checks it against the intended network, flags missing memo/tag for exchange deposits and known token-contract addresses. Verdict: ok, caution, do_not_send or incomplete. Cannot see balances or sanctions lists.

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": {
      "address": "<address>"
    },
    "name": "check_crypto_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoNoMemo / destination tag the user plans to include (TON, XRP, XLM, ...)
addressYesDestination address to check
networkNoNetwork the user intends to send on (omit to check format only)
recipientNoWho receives: exchange deposit address, own wallet, or someone else

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only, idempotent, closed-world annotations, it discloses that the check is free, enumerates four possible verdicts, and states important visibility limits. It also describes concrete caution triggers, helping the agent avoid treating the verdict as a comprehensive balance, sanctions, or safety assessment.

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?

The description is compact and front-loaded with cost, execution mode, and timing, then moves logically through checks, verdicts, and limitations. Despite packing in substantial detail, it contains no filler or unnecessary invocation instructions.

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

Completeness5/5

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

For a four-parameter, flat-schema tool with complete parameter descriptions and clear safety annotations, this supplies the remaining operational context needed for correct use. Because there is no output schema, listing the verdict values is especially helpful, and the stated limitations prevent overclaiming; only explicit sibling routing could further improve selection guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents all four parameters, so the description does not need to redefine them. It adds useful interaction semantics: the intended network is cross-checked against the address, and memo and recipient context drives missing memo/tag warnings for exchange deposits.

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 gives a concrete pre-send validation purpose and enumerates specific checks: address-family detection, checksum and format validation, network matching, memo/tag checks, and token-contract warnings. Its functional scope is clear, but it does not explicitly differentiate itself from the sibling check_address_poisoning or explain which risks belong to each tool.

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

Usage Guidelines5/5

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

It gives an explicit invocation point—before a user sends or before a support agent confirms a deposit address—and identifies both user and support workflows. "Cannot see balances or sanctions lists" supplies a meaningful boundary, although it does not name an alternative for those needs.

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