Skip to main content
Glama

chain_ens_resolve

Read-onlyIdempotent

$0.005 via x402: resolve ENS in either direction on Ethereum — pass an ENS name (vitalik.eth) to get its 0x address, or pass a 0x address to get its primary ENS name (and avatar when set). The identity read every wallet, payment and UX agent makes to verify who it's sending to, or to display a human-readable name instead of a raw hex address. Live ENS registry; one paid call instead of running your own resolver.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chain_ens_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoENS name to resolve to an address, e.g. vitalik.eth
addressNo0x address to reverse-resolve to its primary ENS name
x_paymentNox402 payment payload (base64) to settle this call; omit to receive the payment terms first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and open-world, so the safety profile is covered. The description adds value beyond them by disclosing the x402 pay-per-call model at $0.005, and that results come from a live registry rather than a cache. It does not explain what happens when a reverse record does not exist, which is the main remaining behavioral gap.

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?

Price and function are front-loaded in the first clause, followed by directionality, use case and differentiation. It is well structured and reasonably tight, though the second sentence leans slightly promotional ('The identity read every wallet, payment and UX agent makes').

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?

With no output schema, the description carries the return-value burden and does so — 0x address in one direction, primary ENS name plus avatar in the other — and explains the x402 payment handshake indirectly via the schema. Missing only the failure behavior for addresses with no reverse record.

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 the baseline is 3, but the description adds real meaning by presenting name and address as mutually exclusive directions of the same operation ('pass a name ... or pass an address'), which the schema's two independent optional properties do not convey. It leaves open the edge case of passing both or neither.

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 plus the bidirectional behavior: a name resolves to a 0x address, and a 0x address reverse-resolves to a primary ENS name (with avatar). Concrete examples (vitalik.eth) and the phrase 'Live ENS registry' make the scope unambiguous against sibling tools, none of which touch ENS.

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

Usage Guidelines4/5

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

Gives clear usage context — verifying who a payment is being sent to and displaying a human-readable name — and frames it as a single paid call replacing a self-hosted resolver. It does not state exclusions or point to any alternative, but no sibling covers ENS resolution, so the guidance is sufficient.

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