Skip to main content
Glama

Aevum: verified trading records

Get a wallet's record

get_record
Read-only

The public Aevum record of an Ethereum wallet (person, bot or AI agent): every call it locked with status (running, verified, abandoned), result (correct/wrong/void), certificate ids, and summary counts. Use for 'is this trader/agent any good?' or 'show me 0x...'s record'.

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

Input Schema

NameRequiredDescriptionDefault
addressYesEthereum address, 0x + 40 hex characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description contributes above that by disclosing the return payload shape (per-call status, correct/wrong/void result, certificate ids, summary counts) and that the data is public. It says nothing about result volume, pagination, or behavior for an address with no record.

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?

Two sentences, zero filler, with the resource definition front-loaded ahead of the usage examples. The dense enumeration of returned fields is information-bearing rather than padding.

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 one-parameter read tool with no output schema, the description covers purpose, return contents, and use cases well. The remaining gap is scale: since every locked call is returned, an agent gets no sense of result size or whether large histories are truncated.

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?

There is a single required parameter with 100% schema description coverage ('Ethereum address, 0x + 40 hex characters'), so the schema fully documents it. The description adds only the context that the address identifies a wallet that may be a person, bot, or agent, which is marginal. Baseline 3 is appropriate when the schema does the work.

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 states a specific resource ('the public Aevum record of an Ethereum wallet') and enumerates exactly what that record holds: locked calls with status, result, certificate ids, and summary counts. It also clarifies the subject can be a person, bot, or AI agent. It never names a sibling tool, so differentiation from check_* or get_agent is implied rather than explicit.

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?

Concrete usage framing is given via two example intents ('is this trader/agent any good?' and 'show me 0x...'s record'), which tells an agent the situations this tool answers. There are no exclusions or named alternatives, so the agent must infer when a sibling wallet-check tool is preferable.

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