xportalx

erc8004_register

Register your AI agent on-chain with ERC-8004 Trustless Agent Identity. Cost: 0.01 USDC. You receive an NFT representing your agent identity.

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": {
      "agentName": "<agentName>",
      "agentDescription": "<agentDescription>",
      "recipientWallet": "<recipientWallet>"
    },
    "name": "erc8004_register"
  }
}

Input Schema

Name	Required	Description
`agentName`	Yes	Name of your agent (e.g., 'MyAwesomeAgent')
`paymentProof`	No	Transaction hash of payment (required after initial 402 response)
`agentEndpoints`	No	Optional array of endpoints [{name, endpoint, version}]
`recipientWallet`	Yes	Your wallet address (0x...) to receive the Agent NFT
`agentDescription`	Yes	Description of what your agent does

Schema Changelog

Changes observed during successful MCP inspections.

First observedJan 31, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description must disclose behavioral traits itself. It mentions cost (0.01 USDC) and output (NFT), which is helpful, but it omits critical behaviors like the two-step payment flow (initial 402 response requiring paymentProof) and any wallet prerequisites. The schema hints at this, but the description does not.

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 short sentences front-load the action and deliver key details (purpose, cost, output) with no unnecessary words. The structure is easy to scan and every word earns its place.

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?

Given the tool's complexity (5 parameters, no output schema, no annotations), the description is somewhat thin. It provides the overall purpose, cost, and output, but not the registration workflow, payment proof steps, or endpoint configuration. The schema covers parameter details, but the description misses the process context needed for correct use.

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 parameters are already well-documented. The description adds marginal value by linking the recipientWallet to the NFT outcome, but it does not explain the paymentProof requirement or endpoint structure beyond schema.

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 uses a specific verb ('Register') and object ('your AI agent on-chain') with the ERC-8004 standard, clearly distinguishing it from sibling tools like verify_agent. It also states the outcome (an NFT), making the purpose unambiguous.

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 description implies when to use the tool (when you want to register an AI agent on-chain) and notes the cost, but it does not provide explicit alternatives or when-not-to-use conditions. There is no reference to verify_agent or other sibling tools for context.

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

All xportalx tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?