Skip to main content
Glama

Aevum: verified trading records

Publish an agent card

publish_agent_card
Idempotent

After the agent's wallet sent the register/update transaction from register_agent and it is mined: submit the transaction hash. Aevum verifies the card on Ethereum (signer, hash, contract) and indexes it so it shows on the agent's record. Safe to repeat.

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

Input Schema

NameRequiredDescriptionDefault
txHashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare that this is a non-read-only, idempotent, non-destructive, open-world operation. The description adds meaningful behavior beyond that: Aevum verifies the card on Ethereum by signer, hash, and contract, and indexes it so it appears on the agent's record. It also reinforces repeat-safety with 'Safe to repeat,' though it does not detail failure modes or timing.

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 three compact sentences with the prerequisite front-loaded before the action and verification behavior. Every sentence contributes useful information, and there is no redundant or vague wording beyond the mildly repetitive but helpful 'Safe to repeat.'

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with annotations covering safety and idempotency, the description provides the essential sequence, verification behavior, and indexing effect. It does not need to document return values because no output schema is provided, and the missing parameter format detail is minor given the clear semantic explanation of txHash.

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?

With only one parameter and 0% schema description coverage, the description carries the burden of explaining txHash. It does so by identifying the parameter as the transaction hash from the mined register/update transaction, which gives the agent enough context to supply the correct value. It does not specify formatting such as a 0x-prefixed hex string, but the meaning is clear.

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 states a specific action: submit the transaction hash after the register/update transaction from register_agent is mined. It also explains the result, that Aevum verifies the card on Ethereum and indexes it so it appears on the agent's record. This clearly distinguishes it from sibling tools like register_agent, which sends the transaction rather than publishing its hash.

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

Usage Guidelines4/5

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

The description gives a clear precondition: use this only after the agent's wallet has sent the register/update transaction from register_agent and it has been mined. It does not explicitly state when not to use the tool beyond that sequencing condition, such as what to do if the transaction is pending or failed, but the primary usage context 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