Skip to main content
Glama

ENS and Basenames resolver (forward and reverse)

ens_resolve
Read-only

ENS and Basenames lookup: name to address, or address to primary name with forward verification. Returns the ETH address, resolver contract, text records (url, avatar, description, Twitter, GitHub, Telegram, and email when set on-chain) and decoded contenthash (IPFS, IPNS, Swarm, Arweave). Sources: ENS Universal Resolver on Ethereum and the Basenames registry on Base, read via PublicNode JSON-RPC; offchain (CCIP-read) names are reported, not followed. Price: $0.002 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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

Input Schema

NameRequiredDescriptionDefault
nameNoASCII ENS name (vitalik.eth) or Basename (jesse.base.eth) for a forward lookup. Mutually exclusive with address.
addressNo0x EVM address for a reverse lookup: its primary name on Ethereum (ENS) and Base (Basenames), checked by forward resolution, plus that name's records.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the resolution sources and RPC provider, the CCIP-read limitation, and a full pricing model including which calls are not charged. That is exactly the behavioral context an agent needs before invoking a paid, open-world read.

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?

Front-loaded with the lookup direction and return payload, then sources, then pricing. It is dense but each clause carries information; the x402/USDC payment detail is slightly heavy but relevant to agents that must budget a call.

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: address, resolver contract, text records with named keys, and decoded contenthash types. Combined with the two-parameter schema, an agent has everything needed to call it correctly.

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: reverse lookups are verified by forward resolution, and the returned record set is enumerated. This tells the agent what each mode yields, not just what to pass.

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?

The description states a specific verb and resource ('ENS and Basenames lookup: name to address, or address to primary name') and covers both directions explicitly. It is clearly distinguishable from DNS/WHOIS siblings by naming the ENS Universal Resolver and Basenames registry as sources.

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?

Usage context is clear: forward lookup for a name, reverse lookup for an address, with the mutual exclusivity documented. It also draws a useful boundary by stating offchain (CCIP-read) names are reported rather than followed, though it does not name alternative sibling tools for plain DNS lookups.

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