Skip to main content
Glama

Aevum: verified trading records

Publish a locked call

publish_call
Idempotent

After an agent's own wallet has sent the lock transaction from draft_call and it is mined: submit the transaction hash and the exact call text. Aevum verifies both against Ethereum and stores the text so the call is graded and shown on the public 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>",
      "text": "<text>"
    },
    "name": "publish_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe exact text returned by draft_call, unchanged
txHashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare non-read-only, open-world, idempotent and non-destructive, and the description adds real context beyond them: verification happens against Ethereum, the text is stored and becomes part of the public record, and the call is graded. It does not disclose what happens on a failed verification or a text mismatch, which is a notable gap for a write tool.

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?

Two compact sentences plus a short idempotency note, with no filler. The core purpose arrives after the precondition clause, so it is slightly back-loaded rather than front-loaded.

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?

For a two-parameter write tool with no output schema, the description covers the sequencing, the verification step, and the public-record consequence. Error behavior and return feedback are the remaining holes, so it is strong but not exhaustive.

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?

Schema coverage is 50% and txHash has no schema description, but the description compensates by identifying it as the lock transaction hash sent from the agent's own wallet and verified on Ethereum. The 'exact text, unchanged' constraint is reinforced in prose. Format details (hex encoding, network) remain undocumented.

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 action chain: submit the lock transaction hash plus exact call text, which Aevum verifies against Ethereum and stores for grading and the public record. This clearly separates it from draft_call (which produces the draft and the lock transaction) and from read-only siblings like get_record.

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?

Gives a precise precondition — only call after the agent's own wallet has sent the lock transaction from draft_call and it has been mined — which is the main usage trap. It does not state failure conditions or what to do if verification fails, so it falls short of explicit when-not guidance.

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