Skip to main content
Glama

Resolve an ENS name or address, with its text records

ens
Read-only

ENS on Ethereum mainnet. A name (vitalik.eth) resolves to its address, and an address resolves to its primary name, accepted only when that name resolves back to the same address. Returns the avatar and the url, com.twitter, com.github, description and email text records when set. A name that is not registered returns 200 with address null. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoENS name, e.g. vitalik.eth
addressNoOr an address, 0x…

Output Schema

NameRequiredDescriptionDefault
nameNo
inputNo
avatarNo
addressNo
recordsNo
sourcesNo
resolverNo
checkedAtNo
disclaimerNo
registeredNo
primaryNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "address": {},
      +    "avatar": {},
      +    "checkedAt": {},
      +    "disclaimer": {},
      +    "input": {},
      +    "name": {},
      +    "primaryName": {},
      +    "records": {},
      +    "registered": {},
      +    "resolver": {},
      +    "sources": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

Goes well past the readOnlyHint/openWorldHint annotations: it discloses the negative-result semantics (unregistered name returns 200 with address null rather than an error) and the payment requirement (x402, $0.002 per successful call, USDC on Base, Solana and 10 more networks, failures not charged). Those are exactly the operational facts an agent needs before calling.

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?

Four compact sentences, front-loaded with the network scope, and each sentence carries a distinct fact (resolution modes, returned records, null-result behavior, pricing). Slightly dense and the payment clause is a long run-on, but nothing is wasted.

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?

Output schema exists, yet the description still usefully enumerates which text records come back, and it covers the two things structured fields cannot: the not-found response shape and the paid-call model. For a two-parameter resolver with rich annotations, no material gap remains.

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%, so both parameters are already documented, and the description largely restates the two input modes rather than adding syntax or precedence rules. It does add the reverse-verification condition for the address path, but leaves the both-provided case and any name-format normalization unaddressed. Baseline 3 is appropriate.

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 ('Resolve an ENS name or address') plus the scope ('ENS on Ethereum mainnet') and the payload ('avatar and the url, com.twitter, com.github, description and email text records'). Bidirectional behavior is spelled out, so an agent can distinguish this from plain EVM address utilities without opening the schema.

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

Usage Guidelines3/5

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

The reverse-resolution rule ('accepted only when that name resolves back to the same address') tells the agent what to expect from address mode, which is real usage guidance. However, there is no explicit when-to-use framing against alternatives such as evm_address or address_parse, and no guidance on how to pick between name and address inputs if both are supplied.

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