Skip to main content
Glama

Resolve ENS names

resolve_name
Read-onlyIdempotent

Resolve ENS names to addresses, e.g. 'What address is vitalik.eth?'. Takes up to 50 names and returns each name's address for one coin: ETH by default, or another chain or currency such as btc, base or sol. A name without an address for the coin returns null. For a name's full profile (text records, avatar, website) use get_profile.

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": {
      "names": "<names>"
    },
    "name": "resolve_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinNoCoin symbol such as eth, btc, sol, base or op, or a numeric coin type (ENSIP-9/11)
namesYes1 to 50 ENS names as the user wrote them

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.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: batching up to 50 names, a single coin per call, a default of ETH, and null results for names lacking an address on that coin.

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 tight sentences: purpose and example first, then batching and coin semantics, then the alternative. Every sentence carries information an agent would otherwise have to infer.

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?

An output schema exists, so return structure need not be spelled out, yet the description still notes that each name's address is returned and when null appears. For a two-parameter batch lookup this is complete enough to call correctly.

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 schema already documents both parameters. The description still adds meaning by stating the ETH default, naming example coins (btc, base, sol), and explaining the null outcome per name, which the schema does not convey.

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 states a specific verb and resource ("Resolve ENS names to addresses") and immediately gives a concrete example, so an agent knows exactly what this tool returns. It also distinguishes the tool from get_profile, which handles the fuller profile.

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?

It gives the canonical use case ("What address is vitalik.eth?") and explicitly routes agents to get_profile when text records, avatar or website are needed. The condition that selects the alternative is stated rather than inferred.

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.