Skip to main content
Glama

Get ENS name history

get_name_history
Read-onlyIdempotent

Get the history of an ENS name, newest first, e.g. 'When was nick.eth registered, renewed or transferred?'. Each event has its time, type, a one-line summary and its transaction. Filter by types (e.g. registration, renewal, transfer, resolver, record, migration) and a date range. Results come from an indexer and can lag the chain by a few blocks.

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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesENS name as the user wrote it, e.g. nick.eth; normalised by the server (ENSIP-15)
limitNoItems per page, 1 to 100. Default: 25
orderNodesc (default): newest first; asc: oldest first
sinceNo
typesNoOnly these event types
untilNo
cursorNocursor from the previous page, to read the next one

Output Schema

NameRequiredDescriptionDefault
asOfNoChain time the indexer's answer reflects
itemsYes
totalNo
cursorNoPass back as cursor for the next page; absent on the last page
partialNoWhy the answer may be incomplete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description then adds genuinely non-obvious context: results come from an indexer and can lag the chain by a few blocks, which matters when an agent is checking whether a recent event has been recorded. Default ordering ('newest first') is also disclosed.

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?

The description is four tight sentences, front-loaded with purpose and the concrete example before the filtering and indexer caveats. A small amount of space goes to return-shape detail ('its time, type, a one-line summary and its transaction') that the output schema already covers.

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?

For a 7-parameter read tool with an output schema, the description covers purpose, filtering, ordering, and the indexer-lag caveat. Remaining gaps (date format for since/until, pagination guidance beyond the cursor field) are largely handled by the schema and output schema.

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 71%, and the description fills some of the gap: it enumerates representative type values (registration, renewal, transfer, resolver, record, migration) and mentions the date-range filter, which the schema leaves undescribed for since/until. It does not explain what format since/until expect, but it adds real meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Get the history of an ENS name') plus a concrete user question ('When was nick.eth registered, renewed or transferred?') that makes the tool's role unmistakable. It does not explicitly contrast itself with the closest sibling, get_name_details, so it stops short of the top score.

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 example question provides a clear usage context, and the description states that results can be narrowed by event types and a date range. There is no explicit when-not-to-use guidance or named alternative (e.g. use get_name_details for current state), leaving that inference to the agent.

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.