Skip to main content
Glama

Caelara Labs On-Chain Intelligence

address_checksum_validator

Validate an EVM address (EIP-55 checksum) or Solana address (base58, 32 bytes) and return the canonical form

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

Input Schema

NameRequiredDescriptionDefault
addressYesAddress to validate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that output is a canonical form (implying normalization on success), but is silent on failure behavior — whether an invalid address raises an error, returns a null, or returns a boolean flag — which is the single most important behavioral trait for a validator. Read-only nature is obvious from "Validate" but never explicitly confirmed.

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?

A single front-loaded sentence with the action, the two supported formats, and the return value. Nothing is padded and no clause is 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 one-parameter tool with no output schema and no annotations, the description covers input formats and the shape of the successful result. The remaining gap is failure semantics, which matters more here than for a typical read tool because the answer ('valid or not') is the point of the call.

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% and the schema only labels the field "Address to validate", so the description's enumeration of accepted input formats (EVM EIP-55, Solana base58 32 bytes) genuinely adds meaning beyond the schema. It does not clarify case-sensitivity handling or whether a non-checksummed EVM address is accepted, leaving a small gap.

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?

States a specific verb ("Validate") and named resources (EVM address with EIP-55 checksum, Solana base58 32-byte address), plus the outcome ("return the canonical form"). No sibling tool in the list performs address validation, so the scope is unambiguous on its own.

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 rather than stated: an agent can infer this is a pre-flight check or normalization step, but the description never says when to call it (e.g. before transferring, before passing an address to another tool) or what to do if validation fails. There are no competing alternatives to route between, which limits the harm but also the guidance.

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