Skip to main content
Glama

Normalise ENS names

normalize_name
Read-onlyIdempotent

Normalise ENS names (ENSIP-15) and compute their namehash and labelhash, e.g. 'Is Nick.ETH a valid name?' or 'What is the namehash of ens.eth?'. Takes up to 50 names; an invalid name returns an error explaining why. Other tools normalise names themselves: use this to check spelling, look-alike characters or hashes. Works offline.

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": {
      "names": "<names>"
    },
    "name": "normalize_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYes1 to 50 ENS names as the user wrote them

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior, and the description adds real context beyond them: batch cap of 50, error-with-explanation on invalid input, and offline operation. It does not discuss ordering or the shape of the hash output, but the output schema covers return values.

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?

Purpose and example phrasings lead, followed by batch/error behavior, sibling differentiation, and the offline note. Every sentence carries information an agent would otherwise have to guess, and nothing is redundant.

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?

For a one-parameter, read-only utility with full schema coverage, rich annotations and an output schema, the description supplies all remaining decision-relevant detail: batch limits, invalid-input behavior, and when to use it instead of relying on sibling tools.

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 `names` array already documents the 1-50 bounds and that the server normalises each entry. The description's mention of 'up to 50 names' and per-name error reporting restates or slightly extends the schema, so the baseline of 3 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?

States a specific verb and resource (normalise ENS names per ENSIP-15) plus the derived outputs (namehash, labelhash), and the quoted example questions make the scope concrete. It also distinguishes itself from siblings by noting that other tools normalise names internally.

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?

Explicitly says when to reach for this tool (checking spelling, look-alike characters, or hashes) and clarifies that other tools already normalise names, so an agent knows this is not a required pre-step. Both the use case and the non-use case are covered.

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.