Skip to main content
Glama

lookup_address

Find the ENS name associated with a blockchain address using the Alchemy MCP Plugin. Input an address to retrieve its corresponding Ethereum Name Service identifier.

Instructions

Lookup the ENS name for an address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe address to lookup

Implementation Reference

  • index.ts:906-919 (registration)
    Registration of the lookup_address tool in the ListToolsRequestSchema handler. Defines the tool name, description, and input schema.
    {
      name: "lookup_address",
      description: "Lookup the ENS name for an address",
      inputSchema: {
        type: "object",
        properties: {
          address: {
            type: "string",
            description: "The address to lookup",
          },
        },
        required: ["address"],
      },
    },
  • Type definition for the input parameters of the lookup_address tool.
    type LookupAddressParams = { address: string };
  • Helper function to validate if arguments match LookupAddressParams type for the lookup_address tool.
    const isValidLookupAddressParams = (args: any): args is LookupAddressParams => {
      return (
        typeof args === "object" &&
        args !== null &&
        typeof args.address === "string"
      );
    };
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 action ('lookup') but does not describe traits like read-only status, potential errors (e.g., invalid address, no ENS name), rate limits, or output format. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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: 'Lookup the ENS name for an address'. It is front-loaded with the core action and resource, with zero wasted words. This makes it easy for an agent to parse quickly.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is minimally adequate but incomplete. It covers the basic purpose but lacks behavioral details (e.g., what happens if no ENS exists) and usage guidelines. For a lookup tool in a blockchain context, more context on failures or output would improve completeness.

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 documented as 'The address to lookup'. The description adds no additional meaning beyond this, such as format details (e.g., Ethereum address) or examples. With high schema coverage, the baseline is 3, as the schema handles 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: 'Lookup the ENS name for an address' specifies the verb ('lookup'), resource ('ENS name'), and target ('address'). It distinguishes from most siblings (e.g., 'get_block_number', 'get_transaction') but not explicitly from 'resolve_ens', which might be a reverse operation. The purpose is specific but lacks sibling differentiation for the closest related tool.

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 prerequisites (e.g., address format), exclusions, or compare to siblings like 'resolve_ens' (which might resolve ENS to address). Without such context, an agent might misuse it or overlook better options.

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