Local MCP

Get Audit Log

get_audit_log

Read-only

Returns recent LMCP tool call history from the local audit log. Each entry shows timestamp, tool name, call source (local/cloud), success status, and duration. Useful for GDPR Article 30 compliance reporting and debugging.

Input Schema

TableJSON Schema

Name	Required	Description
`ok`	No	Filter to successes (true) or failures (false) only (optional)
`tool`	No	Filter to entries for a specific tool name (optional)
`limit`	No	Number of recent entries to return (default 50, max 200)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`entries`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 30, 2026

addedOutput schema / properties / entries / items / properties / confirmed

Added value: +{
+  "description": "For a gated tool (takes confirm): true = the mutation executed, false = preview only. Absent for read-only tools.",
+  "type": "boolean"
+}

First observedJun 30, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare read-only and non-destructive behavior. The description adds scope (recent, local) but no additional behavioral depth beyond that.

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?

Two sentences with front-loaded purpose and no superfluous words; efficiently conveys what the tool does.

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?

Given the presence of an output schema and three optional parameters, the description covers the key aspects. Could mention limit default/max, but generally complete.

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 coverage is 100%, so parameters are fully documented in schema. Description adds no extra meaning or context about parameters.

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 clearly states the tool returns recent LMCP tool call history from the local audit log, listing specific fields. This distinguishes it from siblings as no other tool serves this purpose.

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?

Provides context for use (GDPR compliance reporting and debugging) but does not explicitly mention when not to use or alternatives.

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

All Local MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.