get_agent_validationsFetch up to 100 validation requests and responses for an ERC-8004 agent by ID to inspect its validation history and trust signals.
The latest 100 validation requests and responses for an agent from the ERC-8004 Validation Registry.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes | ERC-8004 agent ID (token ID in the Identity Registry) |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description usefully adds the 'latest 100' result cap, but says nothing about ordering semantics beyond 'latest', pagination past 100, or behavior when an agent has no validations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single tight sentence with zero filler, front-loading the result count and the resource. Nothing needs to be trimmed or moved.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description should characterize the return, and it does: validation requests and responses, capped at the latest 100, from a named registry. Only the pagination/ordering edge case is left implicit, which is a minor gap for a one-parameter read tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single agent_id parameter is fully documented in the schema, including its ERC-8004 Identity Registry token ID meaning. The description adds no format or semantic detail beyond what the schema provides, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific resource (validation requests and responses) scoped to an agent and names the source registry (ERC-8004 Validation Registry), which distinguishes it from siblings like get_agent_feedback. It is clear what the tool returns, though it doesn't explicitly contrast itself with those siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description says what is returned but gives no when-to-use guidance, prerequisites, or alternatives. An agent must infer on its own whether to call this versus get_agent_feedback or get_agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.