Skip to main content
Glama

Search ENS names

search_names
Read-onlyIdempotent

Search ENS names by label, e.g. 'Find names starting with vitalik'. Matches from the start of a label by default, or anywhere with match: contains. Set namespace to basenames to search *.base.eth names. Results come from an indexer and can lag the chain by a few blocks; for one name's authoritative state use get_name_details.

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": {
      "query": "<query>"
    },
    "name": "search_names"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1 to 100. Default: 25
matchNoprefix (default): labels starting with the query; contains: anywhere
queryYesText to look for in names, e.g. vitalik
cursorNocursor from the previous page, to read the next one
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
partialNoWhy the answer may be incomplete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavior the annotations cannot: results come from an indexer and may lag the chain by several blocks, which warns the agent about staleness and justifies the pointer to the authoritative lookup tool. Pagination is only implied by the cursor parameter rather than described, which keeps it just below a 5.

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 purpose and example, then matching semantics, then the indexer caveat and the alternative tool. No redundant wording and no repetition of what the schema already says verbatim.

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?

Output shape is covered by an existing output schema, and the description supplies the remaining decision-relevant context: matching modes, namespace scope, index staleness, and the escape hatch to get_name_details. Nothing an agent needs to call this correctly for a read-only search is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so limit, match, cursor and namespace are already documented with defaults and enums. The description restates default prefix matching and the basenames namespace for *.base.eth, adding light semantic framing but no syntax or edge-case detail beyond the schema; baseline 3 applies.

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 ('Search ENS names by label') and immediately grounds it with a concrete example query. It also distinguishes itself from get_name_details, so an agent can choose between search and lookup without opening the 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?

Explicitly frames the use case (find names by label), explains the default prefix matching versus match: contains, and names the alternative tool plus the condition that selects it ('for one name's authoritative state use get_name_details'). That is a complete when-to-use/when-not mapping.

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.