Skip to main content
Glama

ENS name lookup

blackwood_ens_lookup
Read-onlyIdempotent

Use when you need to resolve an ENS name to an address, reverse-resolve an address to its ENS name, or read an ENS avatar and profile records. Do not use for registering or renewing names, or non-ENS naming such as Solana SNS. Returns JSON with an ENS lookup on Ethereum in one call: the address of a name, the verified primary name of an address (reverse), the avatar and text records such as url, twitter and github for 0.003 USDC per call. Typical response time 2000 ms (p95). Category: Data.

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

Input Schema

NameRequiredDescriptionDefault
nameNoENS name to resolve, e.g. vitalik.eth (send name or address, not both)
textsNoText record keys to read (avatar, url, description, com.twitter, com.github and email when omitted), e.g. ["url", "com.github"]
addressNoEthereum address to reverse-resolve, e.g. 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 (send name or address, not both)
response_formatNoconcise (the default when omitted) keeps the JSON short: long fields such as base64 images or audio come back as separate image/audio content blocks and other long strings are cut with a marker; detailed returns the full JSON

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered structurally. The description adds genuinely new operational context: cost (0.003 USDC per call), p95 latency of 2000 ms, single-call JSON return, and Ethereum as the chain. Rate limits and failure modes are not described, keeping it below a 5.

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?

Three sentences, appropriately front-loaded with the use-when/enum-style trigger before exclusions. Minor redundancy: the second sentence re-enumerates resolve/reverse/records already stated in sentence 1 while folding in pricing and latency, so a little trimming is possible.

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 an output schema present, return values need not be explained, yet the description still restates them; the important extras - cost, latency, chain, category, exclusions - are all supplied. Complete enough that an agent can select and call the tool correctly with no further inference.

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 description coverage is 100%, so all four parameters (name, address, texts, response_format) are already documented in the schema, including the name-or-address exclusivity and the concise default. The description reinforces that invariants but adds no syntax, format, or default detail beyond the structured fields, so the baseline 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?

Names a specific verb+resource triple: resolve an ENS name to an address, reverse-resolve an address to its ENS name, and read avatar/text records. It also draws the boundary against adjacent tools (registering/renewing, non-ENS naming like Solana SNS), so an agent can distinguish it from domain_intel and wallet_* siblings without opening a schema.

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?

Opens with an explicit 'Use when...' trigger list and follows with an explicit 'Do not use for...' exclusion covering registration/renewal and non-ENS naming systems. The only mild gap is that it doesn't name a specific sibling to use instead for non-ENS lookups, but the exclusion condition is fully stated.

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