Skip to main content
Glama

erc8004_get_validation_status

Check the status of an ERC-8004 validation request by providing the request hash to verify completion or progress.

Instructions

Get ERC-8004 validation request status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
request_hashYesValidation request hash (bytes32)

Implementation Reference

  • The handler function that calls the API to retrieve the validation status for the given request hash.
    async (args) => {
      const result = await apiClient.get(`/v1/erc8004/validation/${args.request_hash}`);
      return toToolResult(result);
    },
  • Input schema validation using Zod for the tool.
    {
      request_hash: z.string().describe('Validation request hash (bytes32)'),
    },
  • Registration function for the erc8004_get_validation_status tool.
    export function registerErc8004GetValidationStatus(server: McpServer, apiClient: ApiClient, walletContext?: WalletContext): void {
      server.tool(
        'erc8004_get_validation_status',
        withWalletPrefix('Get ERC-8004 validation request status.', walletContext?.walletName),
        {
          request_hash: z.string().describe('Validation request hash (bytes32)'),
        },
        async (args) => {
          const result = await apiClient.get(`/v1/erc8004/validation/${args.request_hash}`);
          return toToolResult(result);
        },
      );
    }
Behavior2/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 but offers none. It does not indicate whether this is a cached read, what status values are possible (pending/approved/rejected), or the latency characteristics of the validation check.

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

Conciseness4/5

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

Extremely terse at six words, front-loaded with the action verb. No wasted words, though the extreme brevity sacrifices opportunity to add behavioral context that would be valuable given the lack of annotations.

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?

Adequate for a single-parameter tool with complete schema documentation, but gaps remain regarding expected return values or status lifecycle given the absence of an output schema and annotations.

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 coverage is 100%, with the request_hash parameter fully documented as 'Validation request hash (bytes32)'. The description does not add syntax details or examples beyond the schema, which is acceptable given the high schema coverage baseline.

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 uses a clear verb ('Get') and specific resource ('ERC-8004 validation request status'), distinguishing it from siblings like erc8004_get_agent_info and erc8004_get_reputation by targeting the specific validation request lifecycle. However, it does not explicitly clarify when to use this versus checking reputation or agent info.

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?

No guidance provided on when to invoke this tool (e.g., after submitting a validation request) versus alternatives. No mention of polling patterns or prerequisites like having a valid request_hash from a prior operation.

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