Skip to main content
Glama

List names of an address

list_names_for_address
Read-onlyIdempotent

List the ENS names of an address, e.g. 'What names does nick.eth own?'. By default lists names the address owns, manages or holds roles on; relation: resolvesTo lists names whose ETH address is the address, formerOwner names it used to own. Each name says how the address relates to it and whether it is the address's primary name. Set namespace to basenames for *.base.eth names. 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": {
      "address": "<address>"
    },
    "name": "list_names_for_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNoItems per page, 1 to 100. Default: 25
orderNo
cursorNocursor from the previous page, to read the next one
parentNoOnly direct subnames of this name, e.g. base.eth
searchNoOnly names whose label starts with this text
addressYesEthereum address (0x…) or an ENS name resolving to one, e.g. nick.eth
relationNoany (default: owner, manager or role holder), owner, manager, roleHolder, resolvesTo or formerOwner
namespaceNoens (default), or basenames for *.base.eth names on Base

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
addressYes
partialNoWhy the answer may be incomplete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: results come from an indexer and can lag the chain by a few blocks, and each result row carries relation type and primary-name status. That staleness caveat is exactly the kind of thing an agent cannot infer from annotations or schema.

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 purpose and an example, then progressively narrower detail. It is dense but nearly every clause carries information; the middle sentences are semi-colon chained, which makes it slightly harder to scan than a bulleted relation list would be, but nothing is wasted.

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 an output schema present, the description needn't enumerate return fields, and it still tells the agent what each row conveys (relation + primary-name flag). Combined with the indexer-lag warning and relation/namespace semantics, an agent has what it needs to call this correctly; only explicit sibling routing 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 78%, so the baseline is 3. The description goes further by explaining the semantics of the relation enum in query terms (resolvesTo = names pointed at this address, formerOwner = previously held) and by clarifying the namespace switch to *.base.eth, which the schema only states tersely. The remaining parameters (sort, limit, cursor, parent, search, order) are left 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?

Leads with a specific verb+resource ('List the ENS names of an address') and immediately anchors it with a natural-language example query ('What names does nick.eth own?'). The following sentences make clear this is a reverse lookup (address -> names), which distinguishes it from forward-lookup siblings like resolve_name and list_subnames.

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?

Explains the default scope (owned, managed, role-holding names) and then the two non-default modes (resolvesTo, formerOwner), so an agent knows which relation value matches which question. It stops short of explicitly naming a sibling to use instead for e.g. subname enumeration or name metadata, so it is clear context rather than full when/when-not routing.

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.