Skip to main content
Glama

Agent Audit Office

List AAO Grade A agents

list_grade_a
Read-onlyIdempotent

List all agents on AAO's Grade A list in the latest report, ranked by independent payers. 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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world scope, so safety needs no restating. The description adds real value beyond them: data provenance ('AAO's published report'), that only the latest report is used, and the interpretive caveat about non-listing, which prevents misuse of a negative result. It stops short of describing return shape or pagination, keeping it at a 4.

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?

Three short sentences with the core purpose front-loaded and no filler. The trust caveat is well placed after the purpose statement, and the read-only/provenance note closes efficiently; slight redundancy with the annotations' read-only claim.

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 zero-parameter list tool with no output schema, the description covers what is listed, which report version, and how results are ordered, plus an interpretation guardrail. Missing only result-volume or pagination expectations, which is a minor gap at this complexity.

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?

The tool takes zero parameters, so the baseline is 4. The description adds ordering semantics ('ranked by independent payers') that the empty schema cannot convey, though there is no way to control that ordering or page through results.

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 verb and resource ('List all agents on AAO's Grade A list') plus scope ('in the latest report') and ordering ('ranked by independent payers'). It is clear what comes back, though it does not explicitly contrast itself with siblings like lookup_agent for single-agent detail.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the 'Grade A list in the latest report' framing and the caveat that absence from the list is not a verdict of untrustworthiness, which helps an agent interpret results. However, there is no explicit when-to-use statement, no exclusions, and no pointer to lookup_agent or get_report_summary for related questions.

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