Skip to main content
Glama

Get ENS name details

get_name_details
Read-onlyIdempotent

Get an ENS name's ownership and registration state, e.g. 'Who owns ens.eth and when does it expire?'. Returns a one-line summary, status (available, registered, grace, expired, reserved), ENS version, owner, manager and registrant, resolver, expiry and grace period, and whether it is wrapped, can be registered or renewed. Ask for burned NameWrapper fuses or ENSv2 migration readiness with include. To check what one account may do, use get_permissions.

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

NameRequiredDescriptionDefault
nameYesENS name as the user wrote it, e.g. nick.eth; normalised by the server (ENSIP-15)
includeNoExtra details: fuses (wrapped names), migration (moving an ENSv1 name to ENSv2)

Output Schema

NameRequiredDescriptionDefault
nameYesENS name as the user wrote it, e.g. nick.eth; normalised by the server (ENSIP-15)
fusesNoBurned NameWrapper fuses; null when the name is not wrapped
ownerYesWho ultimately controls the name
expiryNoEnd of the registration, grace period excluded; absent when it never expires
statusYes
managerNo
summaryYes
wrappedYesWrapped in the ENSv1 NameWrapper
migratedYesMoved from ENSv1 to ENSv2
resolverYes
availableYesCan be registered now
migrationNo
reachableYesWhether ENS resolution still reaches the name's records
renewableYesCan be renewed now
ensVersionYes
registrantNo
gracePeriodEndNoISO 8601 date and time in UTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds real behavioral context: the enumerated status values (available, registered, grace, expired, reserved) and the fact that include unlocks additional expensive/extra detail such as burned fuses and migration readiness.

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 core purpose and question example, then the routing advice. The middle sentence is a long flat enumeration of return fields, which is dense but reads as a deliberate one-line summary rather than filler.

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?

For a 2-parameter read tool with full schema coverage, an output schema, and complete annotations, the description covers purpose, conditional parameters, and sibling routing without needing to explain return values. Nothing an agent needs to select or call it correctly is missing.

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; the description goes slightly beyond by explaining *why* include exists (burned NameWrapper fuses, ENSv1→ENSv2 migration readiness) rather than just restating the enum values. It adds purpose-level meaning but no syntax or edge-case detail for the name parameter, which the schema already handles.

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 ("Get an ENS name's ownership and registration state") and anchors it with a natural-language example question. It is distinguishable from siblings like get_permissions or get_name_history because it explicitly frames the tool as an ownership/registration state read.

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 explicit routing guidance for the include parameter (fuses, migration) and names get_permissions as the alternative when the question is about what an account may do. It does not cover every plausible alternative (e.g. get_name_history vs this tool), which keeps it from a 5.

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.