Skip to main content
Glama

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

Build ERC-8004 Trustless Agent Registration URI & RFC 9421 Web Bot Auth

build_erc8004_trustless_agent_registration
Read-onlyIdempotent

Generates standard ERC-8004 Identity/Reputation JSON, on-chain Agent URI, x402Support bindings, and RFC 9421 cryptographic bot signature headers.

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

Input Schema

NameRequiredDescriptionDefault
chainIdNoEVM chain ID (default '8453')
agentNameNoAgent identifier name
agentDomainNoHTTPS origin hosting /.well-known/agent.json and /mcp
agentWalletNoAgent 0x settlement wallet
dailyCapUsdcNoBounded daily spend cap in USDC (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 covered. The description adds useful content by naming the four artifacts produced, but it omits important behavior: how the RFC 9421 cryptographic signature is produced with no key/signing parameter in the schema, and what the return payload looks like given there is no output schema. Adequate but with real gaps.

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 front-loaded sentence with no filler, and the generated artifacts are listed first. The density of protocol jargon (ERC-8004, x402Support, RFC 9421) makes it a heavy read, but every term carries information.

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?

This is a multi-artifact generator with five optional parameters and no output schema, so the description must carry more weight than usual. It enumerates the outputs but does not explain the returned structure, ordering of use (register URI before publishing well-known file), or signing/key handling, leaving an agent to discover these by calling it.

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% and every parameter carries its own description (defaults for chainId and dailyCapUsdc, meaning of agentDomain and agentWallet). The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 specific verb ('Generates') and enumerates concrete artifacts: ERC-8004 Identity/Reputation JSON, on-chain Agent URI, x402Support bindings, and RFC 9421 signature headers. An agent can tell this is a builder/generator tool rather than the verification sibling. It does not explicitly distinguish itself from sibling build_* tools, keeping it below a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. It does not say whether this should be run before verify_counterparty_agent_trust_and_escrow, whether a domain/well-known file must already exist, or what happens if optional params are omitted (shell defaults are only visible in the schema). Usage is left entirely to inference from the name.

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.