Skip to main content
Glama

Teardrop

by dev.teardrop.api
OverviewDiscussionsAdmin

Resolve Ens

resolve_ens
Read-only

Resolve an ENS name (e.g. 'vitalik.eth') to an Ethereum address, or an address to its primary ENS name, with avatar text record when available. Mainnet only.

Use when: Use only when no 0x address is available and a name must become an address (or vice versa for attribution). If a 0x address is already present in the task or session, use it directly — resolution is redundant and adds latency.

Limitations: Ethereum mainnet ENS only — no other chains or naming services. Reverse records are optional on ENS, so a valid address may legitimately have no primary name.

Alternatives: get_wallet_portfolio, get_wallet_history

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesENS name (e.g. 'vitalik.eth') to resolve to an address, or an Ethereum address (0x…) for reverse lookup to a primary ENS name.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
errorNo
avatarNo
addressYes
resolvedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / name / title
      Added value: +"Name"
    • addedInput schema / title
      Added value: +"mcp_resolve_ensArguments"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The readOnlyHint annotation already signals the operation is safe, and the description adds genuinely useful behavioral context: mainnet-only support, reverse records being optional, and avatar text records being returned only when available. This goes beyond what annotations provide.

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?

The description is well-structured with clear 'Use when', 'Limitations', and 'Alternatives' sections, and the core purpose is front-loaded. Every sentence adds value, and the exclusion advice is placed immediately after the purpose.

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?

With a single required parameter, a complete schema description, a read-only annotation, and an output schema, the description covers the important edge cases: mainnet-only behavior, optional reverse records, and the directive to skip resolution when unnecessary. Nothing essential 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%, and the schema already explains that `name` accepts either an ENS name or an Ethereum address for reverse lookup. The description does not add parameter-level semantics beyond the schema except for noting the avatar text record, which is return-value context rather than parameter meaning.

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 clear verb and resource: resolving an ENS name to an Ethereum address and reverse-resolving an address to its primary ENS name. It adds scope ('Mainnet only') and a concrete example ('vitalik.eth'), making the tool's purpose unmistakable and distinct from the sibling tools.

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 an explicit usage rule: use only when no 0x address is available, and avoid resolution entirely when a 0x address is already present. It also names alternatives and lists limitations, which is strong when-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Teardrop toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources