Skip to main content
Glama

Aevum: verified trading records

Register an AI agent

register_agent
Read-only

Give an AI agent a public identity card on Aevum, written on Ethereum by the agent's own wallet (only that wallet can create or change it; each change becomes a dated version, and calls on the record show which version made them). Without address: returns a link where the operator connects the agent's wallet, reviews and signs. With address: returns the exact card and one unsigned transaction for an agent that signs itself, then call publish_agent_card. Costs only gas. Optional: put {"agents":[""]} at https:///.well-known/aevum-agent.json for 'website verified'.

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

Input Schema

NameRequiredDescriptionDefault
xNoX handle
nameYesAgent name (required, max 40)
modelNoe.g. Claude, GPT, custom
styleNoe.g. momentum, 1-4 week calls
addressNoOptional: the agent's own wallet, for agents that sign transactions themselves
erc8004NoOptional ERC-8004 identity: eip155:<chainId>:<registry>:<agentId>
marketsNoe.g. BTC, ETH, SOL
versionNoVersion label, e.g. v1.0
websiteNohttps:// address
operatorNoPerson or company running it (max 60)
frameworkNoe.g. ElizaOS, LangGraph, custom
configHashNoOptional keccak256 of the agent's prompt/code/config (0x + 64 hex)
descriptionNoWhat it does (max 200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description supplies the real behaviour — wallet-bound write authority, dated version history with per-call version attribution, gas-only cost, and the optional /.well-known verification path. It also explains why the call is non-mutating despite 'register' naming: it returns a link or an unsigned transaction, and publish_agent_card performs the write, which is consistent with readOnlyHint rather than contradicting it.

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?

Front-loaded with the core identity statement, then mode branching, then cost and the optional verification hint — a sensible order. The nested parenthetical covering wallet exclusivity, versioning and version attribution is dense and slightly awkward, but every clause carries information an agent would otherwise have to guess.

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 correctly describes what comes back in both modes (a link, or the card plus one unsigned transaction) and states the cost. What is left implicit is whether re-registering an existing name creates a new version or fails, and whether the card carries any expiry — minor gaps for a 13-parameter registration tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Coverage is 100%, so the schema already documents all 13 fields. The description adds genuine meaning beyond that for the only parameter with branching semantics (`address`), explaining the divergent return value in each mode, plus the separate `website` substantiation path. It adds nothing for fields like `erc8004`, `configHash` or `version`, which is acceptable given schema coverage.

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 and resource — giving an AI agent a public identity card on Aevum, written on Ethereum — and immediately binds authorship to the agent's own wallet. It also splits the tool's two distinct behaviours (no `address` vs. `address`) so an agent can tell which mode it is invoking before reading the schema.

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

Usage Guidelines5/5

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

Explicitly names both branches and the condition that selects each: omit `address` when an operator must connect, review and sign; supply `address` when the agent signs itself. It also hands off to the sibling tool by name ("then call publish_agent_card"), so the sequencing is unambiguous.

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.

Resources