Skip to main content
Glama

Wallet Address Check

wallet_address_check
Read-onlyIdempotent

Check one crypto wallet address: which chain it belongs to (EVM, TRON, Bitcoin, Solana — from the format alone), whether its checksum is valid (EIP-55, Base58Check, bech32/bech32m), whether it is on the US Treasury OFAC SDN sanctions list (read daily) or among the addresses the FBI published in an alert (the Binance theft of October 2026, 628 addresses), whether Tether has frozen USDT at it (Ethereum and TRON addresses, read from the USDT contract), and how many pages DechoNet's phishing check judged dangerous showed it. Listed means on that day's list, not a finding about the owner; not listed is not a statement that the address is clean (most scam addresses are on no list). Balances, transaction history and the owner are not looked at — see 'Not checked'. The address is not stored. Use crypto_check_before_sign to judge an address together with the page that asked and the wallet request. Read-only; no API key; rate-limited.

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": "wallet_address_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesWallet address (0x…, T…, bc1…/1…/3…, or a Solana address)

Output Schema

NameRequiredDescriptionDefault
kpisNoKey metrics as label/value pairs
gradeNoLetter grade (A+ to F) when the tool grades the target
scoreNo0-100 score when the tool scores the target
issuesNoDetected problems, severity-rated
statusYesOverall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown'
actionsNoRecommended next actions, most important first
summaryNoOne-paragraph interpretation of the result
receiptsNoSigned observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature.
reportUrlYesHuman-facing interactive report for this exact lookup on dechonet.com
observationNoHow much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover read-only and idempotency, yet the description adds substantive behavior: no API key required, rate-limited, the address is not stored, sanction lists are read daily, and Tether freeze data is read from the USDT contract for Ethereum/TRON only. It also pre-empts the most likely misreading by defining 'listed' as presence on that day's list, not a finding about the owner, and warns that not-listed is not a clean verdict.

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?

The opening is well front-loaded with verb and resource, and nearly every clause carries information. However, the body is one very long sentence laced with nested parentheticals (dates, address counts, chain lists), which makes the dense caveats harder to scan than a short bulleted structure would.

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?

An output schema exists, so return values need not be explained, and the description instead spends its words on the interpretive hazards that actually matter: list-snapshot semantics, false-negative risk, excluded data, and privacy of the input. Nothing an agent needs to call this correctly is missing.

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?

With one required parameter and 100% schema description coverage, the schema already documents the input and its accepted formats. The description adds the useful fact that chain membership is inferred from the format alone, but it contributes little else about the parameter beyond that, so the baseline for high coverage applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Check one crypto wallet address') and enumerates exactly what is checked: chain derivation from format, checksum validation (EIP-55, Base58Check, bech32/bech32m), OFAC SDN, FBI-published addresses, Tether freeze status, and phishing-page counts. It explicitly separates itself from the sibling crypto_check_before_sign, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines4/5

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

Gives clear routing guidance: use crypto_check_before_sign when judging an address together with the page that asked and the wallet request, implying this tool is the single-address primitive. It also bounds scope with 'Balances, transaction history and the owner are not looked at — see "Not checked"'. There is no explicit when-not-to-use statement beyond that scope bound, so a 4 rather than a 5.

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