Skip to main content
Glama

Re-read ERC-8004 feedback proofOfPayment

check_8004_agent
Read-onlyIdempotent

check_8004_agent loads one ERC-8004 Reputation Registry feedback on Base by default (chain eip155:8453), fetches its feedbackURI JSON, re-reads proofOfPayment on chain, and returns the same verdict and checks as GET /api/v1/erc8004/check. Pass agentId and client or feedbackIndex. verdict is verified, verified_payment_unlinked_client, mismatch, no_proof, or unreadable.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agentId": "<agentId>"
    },
    "name": "check_8004_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoCAIP-2 chain id. The default is eip155:8453 (Base).
clientNoEVM address of the feedback client (0x…). Pass client or feedbackIndex.
agentIdYesERC-8004 agent token id on that chain.
feedbackIndexNoFeedback index for that client. Pass client or feedbackIndex.

Output Schema

NameRequiredDescriptionDefault
as_ofYes
chainYes
checksYes
agentIdYes
reasonsNo
sourcesYes
verdictYes
feedbackYes
clientAddressYes
feedbackIndexYes
proofOfPaymentYes
unreadable_reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / checks / properties / proof_chain
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / checks / properties / proof_source
      Added value: +{
      +  "enum": [
      +    "proofOfPayment",
      +    "rollup_transactions"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / unreadable_reason
      Added value: +{
      +  "enum": [
      +    "proof_tx_not_found_on_known_chains"
      +  ],
      +  "type": "string"
      +}
  2. Added

TDQS

A3.5/5.0
Behavior3/5

Does 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 fully covered. The description adds real context beyond that: the default chain (eip155:8453/Base), the intermediate fetch of feedbackURI JSON, the on-chain re-read, and the equivalence to GET /api/v1/erc8004/check. It stops short of stating failure modes beyond the verdict list (e.g., what happens when the feedbackURI is unreachable), so it earns a solid but not top score.

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?

It is a single dense sentence, front-loaded with the action and resource, and every clause carries information (default chain, fetch step, on-chain re-read, verdict enumeration). It would read better split into two sentences, but there is no filler.

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?

With an output schema present, the description need not explain return shapes, and it helpfully enumerates the possible verdict values anyway. Combined with the default chain and the REST-endpoint equivalence, an agent has enough to call it correctly; only the sibling boundary and error behavior remain unstated.

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%, so the baseline is 3. The description only restates the constraint 'Pass agentId and client or feedbackIndex' and the Base default, both of which the schema already documents; it adds no syntax, format, or precedence detail (e.g., what happens if both client and feedbackIndex are supplied).

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 names a concrete verb and resource: it loads one ERC-8004 Reputation Registry feedback, fetches the feedbackURI JSON, and re-reads proofOfPayment on chain. That is far more specific than a tautology, but it never distinguishes itself from the similarly named sibling check_payment_proof, so an agent must infer the boundary between the two.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the scope 'one ... feedback' plus 'Pass agentId and client or feedbackIndex' tells an agent how to scope a single lookup. There is no explicit statement of when to prefer this tool over check_payment_proof or the other check_* siblings, and no when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.