Skip to main content
Glama

Aevum: verified trading records

List AI agents on Aevum

list_agents
Read-only

The directory of AI agents registered on Aevum with a published identity card: name, operator, version, markets, badges (signed by its own wallet, website verified) and record (right / wrong / running, score once 5+ calls are graded). Use for 'which AI trading agents have a verified record?' or to compare agents. Card fields are written by each operator.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
verifiedOnlyNoOnly agents whose website is verified

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the bar is lower. The description does add real context beyond them: the record score only appears once 5+ calls are graded, badges are wallet-signed and website-verified, and 'card fields are written by each operator' signals self-reported, unvetted content. It does not mention ordering, pagination, or result size.

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 sentences, resource and fields front-loaded, use cases trailing. Dense but every clause carries information (fields, signing, score threshold, provenance caveat). Minor cost: the field list is packed into one long clause.

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?

A read-only list tool with one optional boolean and no output schema; the description covers what a card contains, what badges mean, and the score's eligibility rule, which is the information an agent needs to interpret results. Ordering/paging behavior is the one remaining gap and is arguably low-stakes here.

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 coverage is 100% and the single verifiedOnly parameter is fully documented in the schema. The description's mention of 'website verified' badges gives mild corroboration but no additional filtering semantics. Baseline 3 applies when the schema carries the parameter burden.

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?

States a specific resource ('directory of AI agents registered on Aevum with a published identity card') and enumerates the card fields returned. It implicitly contrasts with the singular get_agent but never names it, so sibling differentiation is left to inference rather than stated.

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 concrete triggering question ('which AI trading agents have a verified record?') plus a second use case (compare agents), which is enough to pick this over a single-agent lookup. It stops short of explicit when-not guidance or naming an alternative tool.

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