Skip to main content
Glama

resolve_ens

Convert Ethereum Name Service (ENS) domain names into blockchain addresses using the Alchemy MCP Plugin. This tool resolves human-readable ENS names to their corresponding wallet or contract addresses.

Instructions

Resolve an ENS name to an address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe ENS name to resolve
blockTagNoThe block tag to use for resolution

Implementation Reference

  • TypeScript type definition for input parameters of resolve_ens tool.
    type ResolveEnsParams = { name: string; blockTag?: string | number };
  • Validator function to check and type guard ResolveEnsParams.
    const isValidResolveEnsParams = (args: any): args is ResolveEnsParams => {
      return (
        typeof args === "object" &&
        args !== null &&
        typeof args.name === "string" &&
        (args.blockTag === undefined ||
          typeof args.blockTag === "string" ||
          typeof args.blockTag === "number")
      );
    };
  • index.ts:888-905 (registration)
    Tool registration in the ListTools response, defining name, description, and input schema for resolve_ens.
    {
      name: "resolve_ens",
      description: "Resolve an ENS name to an address",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "The ENS name to resolve",
          },
          blockTag: {
            type: "string",
            description: "The block tag to use for resolution",
          },
        },
        required: ["name"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It doesn't disclose whether this is a read-only operation, what happens with invalid names, rate limits, authentication requirements, or error conditions. The description states what the tool does but not how it behaves.

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 a single, efficient sentence that states the core functionality without any wasted words. It's appropriately sized for a simple lookup tool and front-loads the essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple resolution tool with good schema coverage but no annotations or output schema, the description is minimally adequate. It explains what the tool does but lacks behavioral context and doesn't address the reverse lookup alternative. The description meets basic requirements but leaves gaps in usage guidance.

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?

The schema has 100% description coverage, so parameters are well-documented in the structured data. The description adds no additional parameter semantics beyond what's already in the schema, which is acceptable but not value-adding. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('resolve') and resource ('ENS name'), making it immediately understandable. However, it doesn't differentiate from sibling 'lookup_address' which performs a reverse operation, missing an opportunity for full distinction.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention the sibling 'lookup_address' tool for reverse resolution or clarify typical use cases for ENS resolution, leaving the agent without contextual usage direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/itsanishjain/alchemy-sdk-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server