Skip to main content
Glama
5ajaki

MCP Etherscan Server

by 5ajaki

get-ens-name

Resolve Ethereum addresses to their ENS names using Etherscan's API. Input an address in 0x format to retrieve the associated ENS domain name.

Instructions

Get the ENS name for an Ethereum address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesEthereum address (0x format)

Implementation Reference

  • Executes the 'get-ens-name' tool by validating the input address with AddressSchema, calling EtherscanService.getENSName, and formatting the response as text.
    if (name === "get-ens-name") {
      try {
        const { address } = AddressSchema.parse(args);
        const ensName = await etherscanService.getENSName(address);
        const response = ensName
          ? `ENS name for ${address}: ${ensName}`
          : `No ENS name found for ${address}`;
        return {
          content: [{ type: "text", text: response }],
        };
      } catch (error) {
        if (error instanceof z.ZodError) {
          throw new Error(
            `Invalid input: ${error.errors.map((e) => e.message).join(", ")}`
          );
        }
        throw error;
      }
    }
  • Zod schema used to validate the 'address' input parameter for the get-ens-name tool (and others).
    const AddressSchema = z.object({
      address: z
        .string()
        .regex(/^0x[a-fA-F0-9]{40}$/, "Invalid Ethereum address format"),
    });
  • src/server.ts:146-160 (registration)
    Registers the 'get-ens-name' tool in the ListTools response, including its description and input schema.
    {
      name: "get-ens-name",
      description: "Get the ENS name for an Ethereum address",
      inputSchema: {
        type: "object",
        properties: {
          address: {
            type: "string",
            description: "Ethereum address (0x format)",
            pattern: "^0x[a-fA-F0-9]{40}$",
          },
        },
        required: ["address"],
      },
    },
  • Core implementation that resolves the Ethereum address to its ENS name using ethers.EtherscanProvider.lookupAddress.
    async getENSName(address: string): Promise<string | null> {
      try {
        const validAddress = ethers.getAddress(address);
        return await this.provider.lookupAddress(validAddress);
      } catch (error) {
        if (error instanceof Error) {
          throw new Error(`Failed to get ENS name: ${error.message}`);
        }
        throw error;
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'gets' an ENS name, implying a read-only operation, but does not specify behavioral traits like error handling (e.g., if no ENS name exists), rate limits, authentication requirements, or response format. This leaves significant gaps in understanding how the tool behaves in practice.

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 directly states the tool's purpose without unnecessary words. It is front-loaded with the core functionality, making it easy to understand quickly, and every part of the sentence contributes essential information.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete for a tool that performs a lookup operation. It does not explain what is returned (e.g., the ENS name string or null if not found), error conditions, or any dependencies, leaving the agent with insufficient context to use the tool effectively beyond basic parameter input.

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 input schema has 100% description coverage, with the 'address' parameter clearly documented. The description adds no additional meaning beyond what the schema provides, such as explaining ENS name resolution specifics or edge cases. With high schema coverage, the baseline score of 3 is appropriate as the 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 ('Get') and resource ('ENS name'), and identifies the target ('Ethereum address'). However, it does not explicitly differentiate from sibling tools like 'get-contract-abi' or 'get-transactions', which might also involve Ethereum addresses but serve different purposes.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or specific contexts for usage, such as when an ENS name lookup is needed compared to other address-related operations offered by sibling tools.

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/5ajaki/mcp-etherscan-server'

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