Skip to main content
Glama

List subnames

list_subnames
Read-onlyIdempotent

List the direct subnames of an ENS name, e.g. 'What subnames does ens.eth have?'. Expired subnames are left out unless includeExpired is set. 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": "list_subnames"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesENS name as the user wrote it, e.g. nick.eth; normalised by the server (ENSIP-15)
sortNo
limitNoItems per page, 1 to 100. Default: 25
orderNo
cursorNocursor from the previous page, to read the next one
searchNoOnly subnames whose label starts with this text
includeExpiredNo

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.4/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 adds genuinely new behavior: expired subnames are filtered out by default, and results come from an indexer that can lag the chain by a few blocks — important eventual-consistency context an agent would otherwise miss.

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?

Three short sentences, front-loaded with the core action and scope, then default filtering, then data-freshness caveat. No filler or redundant restatement of the title.

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?

With 7 parameters and a documented output schema, the description covers the essentials an agent needs: scope, default exclusion, and staleness. Minor gaps remain around sort/order enum meaning and how paging interacts with limit/cursor, but these are partly schema-handled.

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 57%, and the description compensates for the main gap by explaining includeExpired, which has no schema description of its own. It does not explain the sort/order enums or pagination flow via cursor, leaving those to the schema.

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 ('List the direct subnames of an ENS name'), with 'direct' marking the non-recursive scope that separates it from broader lookups like get_name_details or search_names. The example user question anchors the intent unambiguously.

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 ('What subnames does ens.eth have?') gives clear context for when to reach for this tool, and the includeExpired note clarifies default behavior. It stops short of naming an explicit alternative or exclusion case (e.g., when to use search_names or create/update_subname instead).

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.