Skip to main content
Glama

ZK Provenance, RFC 9421 Web Bot Auth & Counterparty KYB MCP

Verify Counterparty Agent KYB (ERC-8004 / A2A / MCP) & Build Bounded Payment

verify_counterparty_agent_trust_and_escrow
Read-onlyIdempotent

Audits an external AI agent's live A2A/MCP/x402 manifests and on-chain wallet history before generating bounded USDC settlement calldata.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "verify_counterparty_agent_trust_and_escrow"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainIdNoEVM chain ID (default '8453')
targetUrlNoCounterparty agent HTTPS URL
paymentUsdcNoProposed USDC payment amount (default 10)
counterpartyWalletNoCounterparty 0x wallet address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive, and the description is consistent with them: it fetches live external manifests (open-world) and only produces calldata rather than broadcasting a transaction. It adds no detail on failure behavior when a counterparty is untrusted, latency, rate limits, or what the audit verdict looks like.

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?

A single compact sentence with the verb and scope front-loaded and no filler. The density of protocol jargon (A2A/MCP/x402) makes it slightly harder to parse than it needs to be, but nothing is wasted.

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?

With no output schema, the description should say what an agent gets back (trust verdict, calldata, or both) and what happens when verification fails; it only mentions 'generating bounded USDC settlement calldata'. For a tool that combines external network auditing with calldata generation, that leaves a meaningful 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 description coverage is 100%, so all four parameters (chainId, targetUrl, paymentUsdc, counterpartyWallet) are already documented in the schema, including defaults. The description adds no parameter-level meaning beyond that 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?

States a specific verb (audits) with a specific resource (external agent's live A2A/MCP/x402 manifests and on-chain wallet history) and the downstream artifact (bounded USDC settlement calldata). This clearly separates it from registration builders or swap simulators, though it never names a sibling explicitly.

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?

The phrase 'before generating bounded USDC settlement calldata' implies a pre-payment due-diligence step, which is usable ordering guidance. There is no explicit when-not guidance, no stated prerequisites, and no named alternative for agents that only want to build calldata without the audit.

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.