Skip to main content
Glama

get_audit_log

Retrieve the protocol audit log to review registrations, activations, violations, and resolutions during swarm sessions, with filters for action, protocol, and result limits.

Instructions

Get the protocol audit log. Shows all protocol operations including registrations, activations, violations, and resolutions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectDir": "<projectDir>"
    },
    "name": "get_audit_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum entries to return (default: 20)
actionNoFilter by action type
formatNoOutput format (default: pretty)
offsetNoSkip first N entries (default: 0)
projectDirYesAbsolute path to the project directory
protocolIdNoFilter by protocol ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. "Get" and "Shows" imply a read-only retrieval, but the description says nothing about ordering of entries, whether it is project-scoped, or retention behavior. For a plain read tool this is adequate but thin.

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, front-loaded with the resource and followed by the content enumeration. Slight redundancy between "audit log" and "all protocol operations" but nothing wasted.

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 six fully documented parameters and no output schema, the description covers what an agent needs to know to call it. The remaining gap is ordering/pagination behavior and differentiation from the violations-specific sibling, which would be worth one more sentence.

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 filtering by action, protocolId, limit, offset, and format is already fully documented in the schema. The description adds no meaning beyond that — no mention that filtering or pagination is supported — so the baseline 3 applies.

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 ("Get the protocol audit log") and enumerates the record types it contains (registrations, activations, violations, resolutions). It is clear what the tool returns, though it does not explicitly distinguish itself from a sibling like get_violations, which appears to be a narrower view of the same domain.

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 phrase "all protocol operations" suggests this is for a comprehensive audit trail rather than a targeted lookup, but no when-to-use/when-not-to-use guidance or alternatives are stated. An agent must infer that get_violations is the narrower option.

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