Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Address checksum (EIP-55): validate and format an EVM address

evm_checksum
Read-only

Address checksum for any EVM address: validates it and returns the EIP-55 checksummed form, saying whether the input was all lower case, all upper case, correctly checksummed or mixed case with a wrong checksum (a likely typo). Works for every EVM chain. Use before sending funds or storing an address; for whether it is a contract use _is_contract. Example: address=0xd8da6bf26964af9d7eed9e03e53415d37aa96045. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
addressYes0x address (40 hex characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is largely covered; the description still adds real value with cost behavior ($0.01/call, first 25 free, failed calls free) and the note that repeats are billed, which explains the idempotentHint=false signal. However, it says nothing about response shape beyond the four classification labels, error behavior for malformed input, or latency, so it is good but not exhaustive.

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?

Well front-loaded: purpose, then outcomes, then scope, then usage routing, then pricing. Slight waste at the end where pricing is stated twice ('Price $0.01/call ... first 25 free; failed calls free' and 'each call is charged, so repeats are not free'), which could be one sentence.

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?

With no output schema, the description carries the return-value burden and does so by enumerating the four result classifications and the likely-typo interpretation. Combined with the single required parameter and the safety annotations, an agent has everything needed to call and interpret this tool.

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% and the single parameter is already documented as a '0x address (40 hex characters)'. The description adds a concrete example address, which usefully illustrates the expected format, but no additional semantics such as case-insensitivity of input or handling of non-0x strings.

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 and resource ('validates it and returns the EIP-55 checksummed form') and explicitly separates itself from the sibling <chain>_is_contract. The four possible outcomes (all lower, all upper, correctly checksummed, mixed-case typo) make the purpose unmistakable.

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?

Gives an explicit when-to-use ('before sending funds or storing an address') and names the alternative for a different question ('for whether it is a contract use <chain>_is_contract'). It also scopes applicability with 'Works for every EVM chain', so the agent knows no chain-specific variant is needed.

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.