Skip to main content
Glama

lookupAddress

Resolve Ethereum addresses to human-readable ENS names using the MCP Ethers Wallet server. Specify network or RPC URL for cross-chain lookups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe Ethereum address to resolve
providerNoOptional. Either a network name or custom RPC URL. Use getAllNetworks to see available networks and their details, or getNetwork to get info about a specific network. You can use any network name returned by these tools as a provider value.
chainIdNoOptional. The chain ID to use. If provided with a named network and they don't match, the RPC's chain ID will be used.

Implementation Reference

  • Registration of the 'lookupAddress' MCP tool using server.tool(), including schema and handler function.
    server.tool(
      "lookupAddress",
      {
        address: z.string().describe(
          "The Ethereum address to resolve"
        ),
        provider: z.string().optional().describe(PROVIDER_DESCRIPTION),
        chainId: z.number().optional().describe(
          "Optional. The chain ID to use. If provided with a named network and they don't match, the RPC's chain ID will be used."
        )
      },
      async ({ address, provider, chainId }) => {
        try {
          const ethProvider = await ethersService.getProvider(provider, chainId);
          
          // Look up the ENS name for an address
          const name = await ethProvider.lookupAddress(address);
          
          if (!name) {
            return {
              content: [{ 
                type: "text", 
                text: JSON.stringify({
                  address,
                  resolved: false,
                  message: "No ENS name found for this address"
                }, null, 2)
              }]
            };
          }
          
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify({
                address,
                name,
                resolved: true
              }, null, 2)
            }]
          };
        } catch (error) {
          return {
            isError: true,
            content: [{ 
              type: "text", 
              text: `Error looking up ENS address: ${error instanceof Error ? error.message : String(error)}`
            }]
          };
        }
      }
    );
  • Handler function that performs ENS reverse lookup: resolves Ethereum address to ENS name using ethers Provider.lookupAddress method.
    async ({ address, provider, chainId }) => {
      try {
        const ethProvider = await ethersService.getProvider(provider, chainId);
        
        // Look up the ENS name for an address
        const name = await ethProvider.lookupAddress(address);
        
        if (!name) {
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify({
                address,
                resolved: false,
                message: "No ENS name found for this address"
              }, null, 2)
            }]
          };
        }
        
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify({
              address,
              name,
              resolved: true
            }, null, 2)
          }]
        };
      } catch (error) {
        return {
          isError: true,
          content: [{ 
            type: "text", 
            text: `Error looking up ENS address: ${error instanceof Error ? error.message : String(error)}`
          }]
        };
      }
    }
  • Zod input schema for the lookupAddress tool, validating address (required string), optional provider and chainId.
    {
      address: z.string().describe(
        "The Ethereum address to resolve"
      ),
      provider: z.string().optional().describe(PROVIDER_DESCRIPTION),
      chainId: z.number().optional().describe(
        "Optional. The chain ID to use. If provided with a named network and they don't match, the RPC's chain ID will be used."
      )
    },
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/crazyrabbitLTC/mcp-ethers-server'

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