Skip to main content
Glama

Get audit log

get_audit_log
Read-onlyIdempotent

Content-free audit events for the account. Requires scope 'usage:read'.

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
limitNo
beforeNoOpaque cursor: a previous next_before.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / before
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 200,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Opaque cursor: a previous next_before.",
      +  "title": "Before"
      +}
    • removedInput schema / properties / before_id
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "minimum": 1,
      -      "type": "integer"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "title": "Before Id"
      -}
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the required OAuth-style scope and the fact that returned events contain no content payload. It says nothing about ordering or whether results are paginated beyond the schema's cursor, which limits it to a 3.

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?

Two short sentences with no filler, front-loading what the tool returns before the access requirement. It is efficient, though 'content-free' is cryptic enough that a clause unpacking it would have earned its space.

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

Completeness2/5

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

There is no output schema, so the description carries the burden of describing what an audit event looks like – and 'content-free audit events' is far too thin to tell an agent what fields to expect (actor, action, timestamp, target). For a zero-required-param read endpoint whose main risk is misinterpreting the return shape, this leaves a significant gap.

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 50% – 'before' is documented as an opaque cursor, while 'limit' has no description at all, only default/min/max bounds. The description compensates for neither, offering no statement about what limit counts or whether events are returned newest-first, so an agent must infer the paging model entirely from 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?

States a specific resource ('audit events for the account') with an implicit retrieval verb, and the qualifier 'content-free' tells the agent the events carry no payload content. However, it does not differentiate from the closest sibling, get_usage, which an agent could easily confuse it with.

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?

The only guidance offered is an authorization prerequisite ('Requires scope usage:read'), which is a precondition, not usage direction. Nothing says when to choose this over get_usage or what an audit log is appropriate for (compliance review, change tracking) versus usage metrics.

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