Skip to main content
Glama

erc8004_get_agent_info

Retrieve on-chain identity information for AI agents, including wallet addresses, metadata, and unique identifiers from the ERC-8004 standard.

Instructions

Get ERC-8004 agent identity info (on-chain ID, wallet, URI, metadata).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYesOn-chain agent ID (uint256)

Implementation Reference

  • The tool handler that calls the API client to fetch the agent info.
    async (args) => {
      const result = await apiClient.get(`/v1/erc8004/agent/${args.agent_id}`);
      return toToolResult(result);
    },
  • Tool registration function using McpServer to define the 'erc8004_get_agent_info' tool.
    export function registerErc8004GetAgentInfo(server: McpServer, apiClient: ApiClient, walletContext?: WalletContext): void {
      server.tool(
        'erc8004_get_agent_info',
        withWalletPrefix('Get ERC-8004 agent identity info (on-chain ID, wallet, URI, metadata).', walletContext?.walletName),
        {
          agent_id: z.string().describe('On-chain agent ID (uint256)'),
        },
        async (args) => {
          const result = await apiClient.get(`/v1/erc8004/agent/${args.agent_id}`);
          return toToolResult(result);
        },
      );
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Get' implies a read operation and the parenthetical clarifies return data, it omits critical behavioral details like whether this requires gas, specific permissions, or network connectivity requirements for on-chain reads.

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 with no waste. The parenthetical elaboration serves a distinct purpose by itemizing the return values, making it front-loaded and information-dense.

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

Completeness4/5

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

Given the single parameter and 100% schema coverage, the description adequately compensates for the missing output schema by enumerating the expected return fields (on-chain ID, wallet, URI, metadata). It is complete for a simple getter tool, though a mention of read-only behavior would strengthen it.

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?

Schema description coverage is 100% ('On-chain agent ID (uint256)'), establishing a baseline of 3. The description adds no explicit parameter guidance, but the schema already fully documents the single required input.

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

Purpose5/5

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

The description provides a specific verb ('Get'), identifies the exact standard (ERC-8004), and clarifies the resource ('agent identity info'). The parenthetical list distinguishes it from siblings like 'erc8004_get_reputation' and 'erc8004_get_validation_status' by specifying exactly which agent data (on-chain ID, wallet, URI, metadata) is retrieved.

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 (e.g., when to query identity vs reputation) or prerequisites for use. Without explicit guidance, an agent cannot determine if this is the correct ERC-8004 tool to invoke.

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/minhoyoo-iotrust/WAIaaS'

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