Skip to main content
Glama

list_audit_events

Read-only

Read public audit events in ascending sequence. Resume with next_after. Corrections link to their predecessor.

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

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNoResults per page. Default: 5.
entry_idNo

Output Schema

NameRequiredDescriptionDefault
eventsYes
next_afterYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's job is to add semantics beyond them. It adds two useful traits the annotations cannot convey: results are ordered ascending, and 'corrections link to their predecessor,' which tells the agent how to interpret event relationships. Rate limits, auth requirements, and default page size behavior are left unstated, keeping it below a 5.

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 terse sentences, front-loaded with the core purpose and no filler. Minor cost: the second sentence names the output token 'next_after' rather than the input parameter `after`, which is compact but slightly ambiguous.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the annotations carry the safety profile. However, for a tool with two undocumented parameters and only 33% schema coverage, the description leaves the meaning of `entry_id` and the cursor-to-parameter mapping unresolved — an agent must guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — only 'limit' is documented in the schema; 'after' and 'entry_id' have no schema descriptions. The description helps only partially: 'Resume with next_after' hints at the `after` cursor but never uses the actual parameter name, and `entry_id` (presumably a filter to one event) is never explained. With low coverage the description should compensate more fully.

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 ('Read public audit events') plus ordering ('ascending sequence'), which distinguishes it from sibling list tools like list_rankings and list_usage_reports. It stops short of explicitly saying how it differs from those siblings, but the resource is distinctive enough to select correctly.

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?

'Resume with next_after' gives implicit pagination guidance, telling the agent how to continue a traversal rather than restart it. There is no explicit when-to-use/when-not guidance and no mention of any alternative tool or prerequisite.

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