Skip to main content
Glama

Name Whisper — ENS Intelligence Layer

by ai.namewhisper
OverviewDiscussionsAdmin

get_expiring_names

Read-only

List ENS names by lifecycle window across the WHOLE market — THE tool for "which names are in premium / on Dutch auction", "names in grace period", "what's expiring soon / about to drop". NOT for the user's own names: it has no wallet filter, so "my names close to premium / in grace / expiring" must go to get_wallet_portfolio with its status parameter (live 2026-09-06 this tool answered "my names that are close to expiring" with 100 strangers' names and the user replied "wtf those arent my names"). Statuses:

  • premium: 90-111 days past expiry, registerable NOW at a decaying premium. Each result includes premiumUsd (decay-curve estimate) and, when the on-chain read landed, premiumEth + firstYearEth (live rentPrice).

  • grace: 0-90 days past expiry. NOT registerable — only renewable.

  • active: registered, expiring within days (they will drop into grace, then premium). Grace/premium results are validated against on-chain state, so renewed or already-released names are filtered out — statuses here are reliable, unlike the coarse EXPIRED flag in search results. Supports length/charType/category/dictionary filters. Use search_ens_names for pattern/price/theme queries instead. SCOPE: every row here has an EXISTING registration moving through a lifecycle window. This tool cannot answer "what is available / unregistered / free to register" in general — those names have no lease to expire, so they are not in this dataset at all. Route "which X are available to register" to search_ens_names, even when X is a digit pattern. Only send a query here when it names a lifecycle window (premium / Dutch auction / grace / expiring soon); "registerable NOW" in the premium line describes that one window, not availability at large. The length/charType filters and sortBy do NOT make this the tool for a plain pattern list: "3-letter numbers sorted by name", "4-letter words", "5-digit names" name no lifecycle window and belong to search_ens_names — sending them here returns a grace/premium dump the user did not ask for.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoFor status "active"/"all": look-ahead window in days (default 30).
limitNoMax results (default 25, max 100)
sortByNoSort order (default expires ascending — closest to dropping first). "grade" = best expected auction outcome first; use it for "which premium names are worth the most / best opportunities".
statusNoLifecycle window: "premium" = in the 21-day post-grace Dutch auction (registerable at a decaying premium), "grace" = 0-90d past expiry (NOT registerable, holder can renew), "active" = registered names expiring within `days`, "all" = any of these.premium
categoryNoCollection slug filter (e.g. "crypto-terms", "999-club")
charTypeNoCharacter composition filter. When this tool is the right one AND the request is for digits — "N-digit", "numeric", or a digit club (999 Club = 3-digit, 10K Club = 4-digit, 100K Club = 5-digit) — set this to "numbers", otherwise letter names of the same length pollute the results. This governs how to FILL this parameter, not whether to call this tool: digit phrasing on its own is not a reason to choose get_expiring_names over search_ens_names.
minGradeNoOnly names graded at least this well (A best). Combine with sortBy:"grade" for the shortlist.
maxLengthNoMaximum label length in CHARACTERS (see minLength note re digits).
minLengthNoMinimum label length in CHARACTERS. Length alone does NOT imply digits — a "4-digit" query needs charType:"numbers" too, or 4-letter names leak in.
dictionaryOnlyNoOnly dictionary words

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / minGrade
      Added value: +{
+  "description": "Only names graded at least this well (A best). Combine with sortBy:\"grade\" for the shortlist.",
+  "enum": [
+    "A",
+    "B",
+    "C",
+    "D",
+    "E"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / sortBy / description
      Previous value: -"Sort order (default expires ascending — closest to dropping first)"New value: +"Sort order (default expires ascending — closest to dropping first). \"grade\" = best expected auction outcome first; use it for \"which premium names are worth the most / best opportunities\"."
    • changedInput schema / properties / sortBy / enum
      Previous value: -[
-  "expires",
-  "length",
-  "social"
-]New value: +[
+  "expires",
+  "length",
+  "social",
+  "grade"
+]
  2. Changed3 schema fields changed
    • changedInput schema / properties / charType / description
      Previous value: -"Character composition filter"New value: +"Character composition filter. When this tool is the right one AND the request is for digits — \"N-digit\", \"numeric\", or a digit club (999 Club = 3-digit, 10K Club = 4-digit, 100K Club = 5-digit) — set this to \"numbers\", otherwise letter names of the same length pollute the results. This governs how to FILL this parameter, not whether to call this tool: digit phrasing on its own is not a reason to choose get_expiring_names over search_ens_names."
    • changedInput schema / properties / maxLength / description
      Previous value: -"Maximum label length"New value: +"Maximum label length in CHARACTERS (see minLength note re digits)."
    • changedInput schema / properties / minLength / description
      Previous value: -"Minimum label length"New value: +"Minimum label length in CHARACTERS. Length alone does NOT imply digits — a \"4-digit\" query needs charType:\"numbers\" too, or 4-letter names leak in."
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, but the description adds substantial behavioral context: there is no wallet filter, results are validated against on-chain state, statuses are reliable unlike the EXPIRED flag, premium results include decay-curve estimates, and every row has an existing registration. This goes far beyond what annotations provide.

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 long and repeats the availability caveat several times, which keeps it from a 5. However, it is front-loaded, uses bullet points effectively, and every paragraph carries routing or scoping information that helps an agent avoid a costly wrong call.

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?

Given 10 parameters, no output schema, and multiple closely related sibling tools, the description is remarkably complete. It covers status semantics, scope exclusions, parameter filling guidance, output field expectations for premium, and explicit routing rules for all likely alternative intents.

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 adds meaningful semantics beyond the schema by explaining how status maps to lifecycle windows, how charType should be set for digit clubs, and why length filters alone do not imply digits. It does not enumerate every parameter, but it gives strategic guidance for the ambiguous ones.

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 names a specific verb ('List'), the resource ('ENS names by lifecycle window'), and the scope ('across the WHOLE market'). It clearly distinguishes itself from get_wallet_portfolio and search_ens_names, so an agent can select it without opening either 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?

Usage guidance is extremely explicit: it says when to use this tool, when not to, and which sibling to use instead. It even gives concrete failure examples like 'my names close to premium' being answered incorrectly, and routes pattern/price/theme queries to search_ens_names.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources