Skip to main content
Glama

Read the audit log

audit_recent
Read-only

Retrieve recent audit log entries to review who called what, outcomes, and timing; filter by principal or outcome. Admin role required.

Instructions

Most recent audit log entries (who called what, outcome, timing). Arguments in entries are already redacted. Requires role: admin.

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": "audit_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax items per page (default 20, max 100)
outcomeNo
principalNo

Output Schema

NameRequiredDescriptionDefault
entriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the description's real contribution is the access-control and privacy context: 'Requires role: admin' and 'Arguments in entries are already redacted'. Those are exactly the behavioral facts an agent needs before calling a sensitive log reader and are not in the schema or annotations.

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?

Three short sentences with zero waste; scope is front-loaded, then the privacy note, then the permission prerequisite in the position an agent will check last before invoking.

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 an output schema present, the description need not explain return values, and it covers scope, redaction and auth. The remaining gap is pagination/ordering behavior for the limit parameter, which is only partially covered by the schema.

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 description coverage is only 33%: limit and outcome have documentation, but principal has none, and the description does not explain it either. The mention of 'who called what' and 'outcome' hints at principal and outcome filtering but adds no filtering semantics or format detail beyond the schema.

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 ('Most recent audit log entries') and names the fields returned (who called what, outcome, timing). It is immediately distinguishable from the CRUD and lookup siblings, none of which touch the audit log, though it could be tighter about ordering/newest-first semantics.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The only usage-relevant cue is the implicit scope of 'most recent', leaving the agent to infer that historical queries are not supported here.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.