Skip to main content
Glama

Aevum: verified trading records

Get an agent's identity

get_agent
Read-only

An AI agent's verified identity card (name, operator, website, framework, model, version...), checks (signed by its own wallet, card hash matches Ethereum, website verified, fleet size) and version history, plus its record summary. Use for 'who is this agent?' or 'is this agent's name real?'.

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_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesEthereum address of the agent

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 declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral detail about what the response contains (self-signed checks, Ethereum hash match, website verification, fleet size), but says nothing about what happens for an unregistered address, whether results are cached, or any auth/rate-limit considerations for an open-world lookup.

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?

One dense sentence front-loads the resource and its payload, followed by a short usage sentence; nothing is wasted. The long parenthetical enumeration is information-dense rather than padded, though it is slightly harder to scan than a structured list.

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?

There is no output schema, so the description carries the burden of describing return values and it does so thoroughly, covering identity fields, verification checks, and version history. The remaining gap is error/empty-result behavior for an unknown or unregistered address.

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?

Only one parameter, and the schema already documents it at 100% coverage as the agent's Ethereum address. The description adds no formatting detail (checksummed vs lowercase, hex prefix) or behavior for a malformed address, so it does not meaningfully exceed the schema baseline.

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 names the resource precisely and enumerates what the card contains (name, operator, website, framework, model, version, signed checks, version history, record summary), so an agent can tell this apart from get_record or get_certificate by content. It stops short of explicitly contrasting itself with those siblings, but the enumerated payload is distinctive enough for selection.

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?

Two concrete trigger phrasings are given: 'who is this agent?' and 'is this agent's name real?', which map cleanly onto identity lookup and verification. There are no explicit exclusions or pointers to alternatives (e.g., list_agents for discovery), so it lands at clear-context-without-alternatives rather than full routing 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