Skip to main content
Glama

Agent Audit Office

Get the AAO report summary

get_report_summary
Read-onlyIdempotent

Get the aggregate figures of the latest AAO report: registered agents, grade counts, liveness, feedback contamination and independent x402 payments. 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": "get_report_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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, idempotentHint, non-destructive, and closed-world, so "Read-only" largely restates structured data. The description does add something beyond annotations — the data provenance ("data from AAO's published report") and the interpretive warning that absence from the Grade A list is not proof of untrustworthiness — but it says nothing about freshness, caching, or how the aggregate figures are computed.

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, front-loaded with the core action and the list of returned figures. The Grade A disclaimer is arguably tangential to invocation, but it is short and directly aids correct interpretation of the returned grades.

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?

With no output schema and no parameters, the description carries the burden of describing the payload, and it does so by naming the specific figures returned. The only gap is that it does not indicate response shape or whether figures are time-stamped to a specific report version.

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?

This tool takes zero parameters, so the schema imposes no semantic burden and the baseline is 4. The description correctly implies a no-argument call by framing the result as a single fixed summary of "the latest" report.

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 verb and resource ("Get the aggregate figures of the latest AAO report") and enumerates the exact metrics returned: registered agents, grade counts, liveness, feedback contamination, x402 payments. That enumeration makes it clear this is an aggregate/ecosystem-level tool rather than a per-agent lookup, though it never names list_grade_a or lookup_agent to make the contrast explicit.

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 only implied: the tool is for reading overall AAO report statistics, and the caveat about the Grade A list hints it should be used to contextualize grading. There is no explicit statement of when to prefer this over lookup_agent or list_grade_a, and no preconditions or exclusions are given.

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