Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_crypto_address_checksum_validator

Validate EVM (EIP-55 checksum) or Solana (base58, 32-byte) addresses and return the canonical form.

Instructions

[On-Chain Intelligence] Validate an EVM address (EIP-55 checksum) or Solana address (base58, 32 bytes) and return the canonical form Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://crypto.caelaralabs.com.

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

Input Schema

NameRequiredDescriptionDefault
addressYesAddress to validate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose chain-specific validation rules, that a canonical form is returned, latency figures, and the outbound endpoint — useful operational context. However, it never says what happens for an invalid address (error vs. a result flag) and there is no output schema, leaving the failure mode undisclosed.

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?

The core capability is front-loaded in the first clause, followed by the operational details (latency, endpoint). The '[On-Chain Intelligence]' tag is mild noise, but overall the text is compact with no filler or repetition.

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?

For a one-parameter validation call with no output schema and no annotations, the definition explains inputs and standards well but stops short of describing the response shape or invalid-input behavior. An agent can select it, but cannot predict the return contract.

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 a single required parameter already described as 'Address to validate'. The description adds chain-specific format expectations (EIP-55, base58/32 bytes) but nothing about the parameter's syntax or accepted variants beyond what the schema conveys. Baseline 3 applies.

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?

States a concrete verb (validate) plus the resource (EVM address / Solana address) and names the specific standards checked (EIP-55 checksum, base58 32 bytes), so scope is unambiguous. It does not explicitly contrast itself with the closely related sibling caelara_docs_address_normalizer, which also deals with address canonicalization, so sibling differentiation is left to inference.

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

Usage Guidelines2/5

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

The description never says when to use this versus alternatives such as the address normalizer or the ERC20 inspector, nor does it state prerequisites. Usage is only implicit in the tool's name and purpose; for a validator that overlaps conceptually with a normalizer, that gap matters.

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

Deploy Server

Other Tools