four02-commerce-mcp

Official

Overview Schema Source Related Servers Discussions Admin

four02_reputation_history

Fetch raw onchain commerce-event history for an ERC-8004 agent from the Four02ReputationRegistry on Ink to review writer contract, event type, and USDC value.

Instructions

Raw commerce-event history for an ERC-8004 agentId from the Four02ReputationRegistry on Ink (append-only; newest last). Each entry shows the recording writer contract, the event type (e.g. invoice_paid_on_time), and the USDC value. Read-only.

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": "four02_reputation_history"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max entries to return (from the newest end)
`agentId`	Yes	ERC-8004 agent ID (decimal string)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 3, 2026

TDQS

A4/5.0

Behavior4/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 — and it does real work: it discloses append-only semantics, that entries are ordered newest-last, that each entry contains the writer contract, event type, and USDC value, and that the operation is read-only. It omits any mention of pagination/truncation behavior or auth/permission requirements.

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?

Three tight sentences, front-loaded with the operation and scope, then ordering and return shape. No filler or restated boilerplate.

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 no output schema, the description usefully enumerates the per-entry fields (writer contract, event type, USDC value) and ordering, which is what an agent needs to interpret results. It stops short of describing pagination behavior or whether the list can be truncated, a minor but real gap.

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%, so both agentId and limit are already documented, including that limit caps entries 'from the newest end'. The description adds only the ordering confirmation ('newest last'), which matches rather than extends the schema. Baseline 3 is appropriate.

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?

States a specific verb+resource: raw commerce-event history for a given ERC-8004 agentId from a named registry. The word 'Raw' implicitly separates it from the aggregate siblings four02_reputation_summary and four02_reputation_reliability, so an agent can route without opening schemas.

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 'Raw ... history' framing suggests this is for unaggregated events versus the summary/reliability siblings, but no when-to-use, when-not-to-use, or explicit alternative is named. Adequate but a clear gap for a tool with three close siblings.

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

Deploy Server