Skip to main content
Glama

Agent Audit Office

Look up an agent in AAO's Grade A list

lookup_agent
Read-onlyIdempotent

Look up an ERC-8004 agent on Base by its ID (chainId:agentId, e.g. 8453:45250). Returns the Grade A details if the agent is on AAO's Grade A list, otherwise status "not_listed". Not being on AAO's Grade A list does not mean an agent is untrustworthy. Read-only; data from AAO's published report.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "lookup_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYeschainId:agentId, e.g. 8453:45250

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, and non-destructive, so the description's added value is in outcome semantics: it names the 'not_listed' status and warns against reading absence as untrustworthiness, and it discloses data provenance (AAO's published report). It does not describe error behavior for malformed IDs or how large the returned Grade A payload is.

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?

Front-loads the identifier format and the successful outcome, then the failure case, then the caveat, then provenance — each sentence carries distinct information with no filler. The only near-redundancy is restating the 8453:45250 example already in the schema, which is minor and aids scanning.

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 lookup with no output schema, the description covers the input format, the success result, the miss result, and the interpretation caveat, which is close to sufficient. It stops short of describing what fields a 'Grade A detail' record contains, leaving the return shape partly unknown.

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 agent_id parameter already documents the chainId:agentId format with the same example. The description repeats that example without adding validation rules, accepted chain IDs, or edge cases, so it adds nothing beyond the schema and baseline 3 applies.

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 verb (look up), a specific resource (an ERC-8004 agent on Base), and the exact key format (chainId:agentId, e.g. 8453:45250). The by-ID framing inherently separates it from the sibling list_grade_a, which would enumerate rather than resolve a single agent.

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?

Clearly scopes usage to resolving one known agent ID and explains the two possible outcomes, including the interpretive caveat that 'not_listed' is not a trust judgment. It does not explicitly say when to prefer list_grade_a or get_report_summary instead, so the when-not guidance is implied rather than stated.

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