Skip to main content
Glama

CoinVet

Validate a crypto address (BTC, EVM, SOL, LTC, DOGE, TRX)

crypto_address_validate
Read-onlyIdempotent

Check a cryptocurrency address offline before using it: Bitcoin legacy/P2SH (base58check), segwit/taproot (bech32/bech32m), Ethereum and all EVM chains incl. Base (EIP-55 checksum via keccak-256), Litecoin, Dogecoin, Tron and Solana. Returns valid, chain, network, type, and the correctly checksummed form. Catches typos and copy errors.

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

Input Schema

NameRequiredDescriptionDefault
chainNoOptional hint, e.g. solana
addressYesThe address to check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, openWorldHint=false and idempotentHint, so safety is covered. The description adds genuine behavioral context beyond that: the check is performed offline, and it names the return fields ('valid, chain, network, type, and the correctly checksummed form'), which tells the agent what it gets and that the tool normalizes the address. It does not say what happens when the optional chain hint disagrees with the detected chain.

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?

Two sentences, front-loaded with the verb and use timing, with no filler. The parenthetical algorithm/encoding names are dense but earn their place by letting an agent self-verify coverage for a particular address format.

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

Completeness3/5

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

With only two parameters and annotations covering safety, the definition is close to complete, and it does describe the return payload in lieu of an output schema. The notable gap is failure semantics: it does not state whether an invalid address yields a result with valid=false or a tool error, nor how a mismatched chain hint is resolved.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning by enumerating the supported chain families, which effectively documents the acceptable domain of the 'chain' hint parameter beyond the schema's single example ('solana'). The 'address' parameter gains the implicit note that any of the listed formats may be supplied.

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?

The description opens with a specific verb and resource ('Check a cryptocurrency address offline') and then enumerates the exact formats supported: Bitcoin base58check, segwit/taproot bech32/bech32m, EVM EIP-55, Litecoin, Dogecoin, Tron and Solana. This makes it trivially distinguishable from siblings such as lightning_address_check or iban_validate without opening any schema.

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?

'before using it' and 'offline' imply a pre-flight validation context, which is useful implied guidance. However, there is no explicit statement of when not to use it, no reference to an alternative tool (e.g. lightning_address_check for Lightning addresses), and no guidance on how to interpret an invalid result versus an error.

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