Skip to main content
Glama

Name Whisper — ENS Intelligence Layer

by ai.namewhisper

extend_subname_expiry

Extend the expiry of an ENS subname in the NameWrapper.

Subnames have their own expiry that cannot exceed the parent name's expiry. This tool extends a subname's expiry.

Who can call this:

  • The parent name owner (always)

  • The subname owner (only if CAN_EXTEND_EXPIRY fuse is burned on the subname)

Use cases:

  • Extending subnames you've issued to users

  • Self-extending your own subname (if CAN_EXTEND_EXPIRY is set)

  • Keeping organizational subnames active

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFull subname to extend (e.g. "sub.coffee.eth")
yearsNoNumber of years to extend from now (default: 1). Cannot exceed parent expiry.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations are all false. The description adds valuable behavioral context: the permission model based on fuse burning, the constraint that extension cannot exceed parent expiry, and the default extension period. It does not disclose idempotency or exact error handling, but overall improves understanding.

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 three paragraphs with a clear front-loaded purpose, followed by a constraint, caller list, and use cases. Every sentence is necessary, no fluff. Highly efficient.

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?

Given the complexity of the tool (permission model, parental expiry constraint), the description covers most key aspects. It lacks explicit behavior when requested years exceed parent expiry (error vs. truncation) and does not mention output. Still, provides sufficient context for most use cases.

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 baseline is 3. The description adds meaning beyond schema by explaining the permission implications for the name parameter (who can call based on ownership and fuses). For the years parameter, it repeats schema info.

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 clearly states the tool extends ENS subname expiry, a specific action on a particular resource (subname in NameWrapper). It distinguishes from sibling tools like renew_ens_name by focusing on subnames and mentioning the fuse system.

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 explicitly lists who can call (parent owner always, subname owner with fuse) and provides use cases. However, it does not mention when not to use or directly compare to alternative tools (e.g., manage_fuses for fuses), leaving some room for ambiguity.

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

All Name Whisper — ENS Intelligence Layer toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation4/5

Most tools have clearly distinct purposes with detailed descriptions, but some pairs (e.g., search_ens_names vs enumerate_entities, batch_purchase vs sweep) could cause confusion due to overlapping functionality. The descriptions help differentiate, but the large number of tools increases ambiguity risk.

Naming Consistency5/5

All tool names use consistent snake_case with a verb_noun pattern (e.g., get_name_details, set_ens_records, batch_create_listings). Naming conventions are uniform and predictable, making it easy to infer tool purpose from the name.

Tool Count4/5

With 44 tools, the server is quite comprehensive, covering a wide range of ENS operations. While this exceeds the typical 3-15 tool count, the scope of the domain (marketplace, registration, agent identity, etc.) justifies the number, and tools are well-organized into logical groups.

Completeness5/5

The tool surface covers the full lifecycle of ENS names: registration, renewal, wrapping, transfers, marketplace actions (listings, offers, purchases), record management, subnames, agent identity, and market intelligence. No obvious gaps are present for an ENS intelligence platform.

Resources