Skip to main content
Glama

Audit log

get_audit_log
Read-only

Who changed what in the workspace, newest first: people, API tokens and agents, with the changed fields and IP (Business plan). Filter by resource_type (monitor, alert_channel, status_page, member, api_token…), action (monitor.updated, or a prefix like monitor.), from and to (YYYY-MM-DD); pass next as before for older entries. Free.

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

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD.
fromNoFirst day, YYYY-MM-DD.
limitNoEntries per page.
actionNoOnly this action, such as monitor.updated, or every action with a prefix, such as monitor.
beforeNoThe next value of the previous page, for older entries.
resource_typeNoOnly entries about this kind of thing, such as monitor, alert_channel, status_page, member or api_token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"Only this action, such as monitor.updated, or every action with a prefix, such as monitor."
    • addedInput schema / properties / before / description
      Added value: +"The next value of the previous page, for older entries."
    • addedInput schema / properties / from / description
      Added value: +"First day, YYYY-MM-DD."
    • addedInput schema / properties / limit / description
      Added value: +"Entries per page."
    • addedInput schema / properties / resource_type / description
      Added value: +"Only entries about this kind of thing, such as monitor, alert_channel, status_page, member or api_token."
    • addedInput schema / properties / to / description
      Added value: +"Last day, YYYY-MM-DD."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds useful behavior: it returns entries newest first, includes actors and changed fields, mentions IP, and notes plan availability. The plan wording is slightly ambiguous ('Business plan' followed by 'Free'), and it omits auth or rate-limit details, so it is not fully complete.

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?

The description is dense and front-loads the key purpose, ordering, and filters. It is somewhat run-on, and the trailing 'Free' is confusing, but most sentences earn their place.

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

Completeness5/5

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

With no output schema, the description carries the burden of explaining return contents, ordering, filtering, and pagination, and it does so thoroughly. It is complete enough for an agent to invoke the tool correctly despite minor plan ambiguity.

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 100%, so the schema already documents all six parameters in detail. The description reinforces the filter examples and pagination semantics but mostly repeats what the schema provides, so the baseline 3 is appropriate.

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?

The description states a specific resource and verb-like action: it returns who changed what in the workspace, newest first, including people, API tokens, agents, changed fields, and IP. This clearly distinguishes it from sibling tools such as get_monitor or list_incidents.

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?

It gives clear context for using the tool and explains how to filter by resource_type, action, from, and to, plus how to paginate with before. It does not explicitly state when not to use it or name alternatives, but the audit-log scope is clear.

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