AgentStamp

bridge_erc8004_trust_check

Check the trust status of an ERC-8004 agent by its numeric ID. Receive a free trust verdict with score indicating trusted or untrusted.

Instructions

Get an AgentStamp trust verdict for an ERC-8004 agent. Free. Returns trusted/untrusted with score.

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": {
      "erc8004_agent_id": "<erc8004_agent_id>"
    },
    "name": "bridge_erc8004_trust_check"
  }
}

Input Schema

Name	Required	Description	Default
`erc8004_agent_id`	Yes	ERC-8004 agent ID (numeric token ID)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Mar 22, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The description discloses that the tool is free and returns trusted/untrusted with a score, which is useful. However, with no annotations provided, the description carries the burden of behavioral disclosure. It lacks details on side effects (e.g., is it read-only?), authentication requirements, rate limits, or any preconditions beyond the ERC-8004 agent ID. This is a minimal disclosure, not misleading but incomplete.

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 extremely concise: 'Get an AgentStamp trust verdict for an ERC-8004 agent. Free. Returns trusted/untrusted with score.' Every fragment adds value, is front-loaded with the primary purpose, and contains no fluff.

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?

For a tool with one parameter, no output schema, and no annotations, the description provides a high-level but sufficient summary of the purpose and expected return format. Missing details include the score's range or threshold, and possible error cases, but overall the description is reasonably complete for the tool's simplicity.

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?

The input schema describes the single parameter 'erc8004_agent_id' as 'ERC-8004 agent ID (numeric token ID)', covering 100% of the parameter semantics. The description itself adds no extra context about the parameter, so the baseline 3 applies as per the schema coverage criterion.

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 clearly states it gets an AgentStamp trust verdict for an ERC-8004 agent, with a specific verb ('Get') and resource ('AgentStamp trust verdict for an ERC-8004 agent'). It includes the output type ('trusted/untrusted with score') and distinguishes from siblings like 'trust_check' by specifying the ERC-8004 and AgentStamp context.

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 context is implied by the description naming the target (ERC-8004 agent) and the AgentStamp trust verdict, but it does not explicitly state when to use this tool over alternatives (e.g., 'trust_check' or 'team_trust_check') or provide any exclusions. There are no alternative tool references or when-not-to-use scenarios.

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