Skip to main content
Glama

Get primary ENS names

get_primary_name
Read-onlyIdempotent

Find the ENS name an address uses (reverse resolution), e.g. 'Which ENS name does 0xd8dA… have?'. Takes up to 50 addresses. A name counts only if it resolves back to the address, so a reverse record cannot claim someone else's name. Returns null for an address without a primary name.

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": {
      "addresses": "<addresses>"
    },
    "name": "get_primary_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinNoChain of the primary name, e.g. base or op for a name set on that L2. Default: eth
addressesYes1 to 50 Ethereum addresses

Output Schema

NameRequiredDescriptionDefault
coinYesCoin symbol such as eth, btc, sol, base or op, or a numeric coin type (ENSIP-9/11)
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered. The description adds genuinely useful behavioral detail: the forward-confirmation rule preventing a reverse record from claiming a name, and the null return for addresses without a primary name.

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 with zero filler: purpose and direction first, then the batch limit, then the resolution rule and null case. Nothing repeats and nothing needs reordering.

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 need not explain return values, yet it still documents the null case. The only gap is whether coin applies to every address in the request, which matters for a batch tool spanning multiple chains.

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 coverage is 100%, so both parameters are documented in the schema itself, warranting the baseline 3. The description restates the 50-address cap already present via maxItems and says nothing about how the coin parameter applies across a batch of addresses.

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 ('Find the ENS name an address uses') and disambiguates the direction with '(reverse resolution)', which separates it from forward-resolution siblings. The question-shaped example makes the intent unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical 'reverse resolution' implies when this applies versus forward resolution, and the example question frames the use case. However, it never explicitly names an alternative such as resolve_name or get_name_details, nor states when not to use this tool.

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.