NameWhisper MCP Server

get_name_details

Get full ENS name details including owner, expiry, creation date, listings, offers, and agent records. Use it to inspect any .eth domain's comprehensive on-chain and market data.

Instructions

Get full details for a specific ENS name including owner, expiry, creation date, tags, active listings (with prices in ETH and USD), active offers, ENSIP-25 agent identity bindings, and ENSIP-26 agent context records. creationDate is always populated — for Vickrey-era names (isVickreyEra=true) it reflects the true first-creation date from the 2017-2019 legacy auction contract; for all other names it reflects the on-chain registration date. Always mention creationDate when answering questions about when a name was created or registered.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	ENS name or label (e.g. "vitalik" or "vitalik.eth")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jul 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It openly discloses a nuanced behavior: creationDate is always populated and its meaning varies for Vickrey-era names (true first-creation date from legacy auction) versus on-chain registration date. It also instructs the agent to always surface creationDate, which is valuable behavioral guidance beyond the raw data.

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?

The description is two sentences: the first concisely lists the data returned, the second explains a subtle data nuance and provides an explicit usage instruction. No words are wasted, and key information is front-loaded.

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?

The description enumerates all major return categories (owner, expiry, creation date, tags, active listings with ETH/USD prices, active offers, ENSIP-25 bindings, ENSIP-26 records) and explains the creationDate edge case. With no output schema, this adequately covers what the agent needs to know about the return value.

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?

The input schema already provides 100% coverage with a description for the single 'name' parameter. The tool description adds no additional parameter-specific semantics, 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?

The description uses a specific verb ('get') and identifies the resource ('full details for a specific ENS name') while enumerating the exact data returned. This clearly distinguishes it from sibling tools like search_ens_names (searching) and get_valuation (valuation only).

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?

The description clearly frames when to use the tool: to retrieve full details for a specific ENS name. It doesn't explicitly reference alternatives, but the context is unambiguous given the sibling tools. It also includes a direct instruction to always mention creationDate when answering creation/registration questions, which guides usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.