Skip to main content
Glama

lookupAddress

Resolve Ethereum addresses by providing a wallet address and optional network details. Use this tool to retrieve and verify blockchain data with ease, supporting custom RPC URLs and chain IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe Ethereum address to resolve
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.
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.

Implementation Reference

  • The handler function that executes the lookupAddress tool logic. It retrieves the ethers provider, calls lookupAddress on it to resolve the address to an ENS name, and returns formatted JSON response or error.
    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 schema defining the input parameters for the lookupAddress tool: required 'address' (Ethereum address), optional 'provider' (network name or RPC URL), optional '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." ) },
  • Registration of the lookupAddress tool using server.tool() in registerCoreTools function, including inline schema and handler implementation.
    // ENS lookupAddress tool 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)}` }] }; } } );

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