Skip to main content
Glama
I4cTime

q-ring

by I4cTime
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

export_audit

Read-onlyIdempotent

Export audit logs as portable JSONL, JSON, or CSV text for archiving, compliance, investigations, or SIEM/analyzer handoff, with optional time filters. Read-only; returns rendered text.

Instructions

[audit] Export the audit log as a portable text artifact suitable for archiving or feeding into another SIEM/analyzer. Use for compliance exports, after-the-fact investigations, or to hand the trail to a non-MCP consumer; prefer audit_log for an in-conversation tail and verify_audit_chain to confirm integrity before exporting. Read-only. Returns the rendered text directly (no JSON wrapper). 'jsonl' is one event per line; 'json' is a single array; 'csv' is a header row plus events. Time filters are applied to the event timestamps before formatting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceNoInclusive lower bound on event timestamp, ISO 8601. Example: '2026-04-01T00:00:00Z'. Omit for no lower bound.
untilNoInclusive upper bound on event timestamp, ISO 8601. Omit for now/no upper bound.
formatNoOutput format. 'jsonl' (default) is most stream-friendly; 'json' is a single array; 'csv' is spreadsheet-friendly.jsonl

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.11.7
    • changedInput schema / properties / format / description
      Previous value: -"Output format"New value: +"Output format. 'jsonl' (default) is most stream-friendly; 'json' is a single array; 'csv' is spreadsheet-friendly."
    • changedInput schema / properties / since / description
      Previous value: -"Start date (ISO 8601)"New value: +"Inclusive lower bound on event timestamp, ISO 8601. Example: '2026-04-01T00:00:00Z'. Omit for no lower bound."
    • changedInput schema / properties / until / description
      Previous value: -"End date (ISO 8601)"New value: +"Inclusive upper bound on event timestamp, ISO 8601. Omit for now/no upper bound."
  2. Addedv0.11.5

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/destructive=false, so 'Read-only' adds little; however, the description adds real context: output is returned as rendered text with no JSON wrapper, and time filters are applied to event timestamps before formatting. Those behavior nuances are not expressible in the annotations.

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?

Well front-loaded: the core action and artifact lead, followed by routing guidance, safety, return shape, and format semantics. Slightly dense and mildly overlaps the enum descriptions in the schema, but no sentence is wasted.

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?

There is no output schema, but the description compensates by describing the return (rendered text, no JSON wrapper) and format-specific rendering. Combined with annotations covering safety, an agent has everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning by spelling out the concrete shape of each format ('jsonl' one event per line, 'json' a single array, 'csv' a header row plus events) and clarifying filter-then-format ordering, which the schema does not state.

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?

States a specific verb+resource (export the audit log) and the artifact type (portable text, no JSON wrapper). It explicitly names the sibling alternatives `audit_log` and `verify_audit_chain`, so an agent can differentiate without opening any schema.

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

Usage Guidelines5/5

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

Explicitly enumerates when to use it (compliance exports, after-the-fact investigations, handing off to a non-MCP consumer) and when to prefer alternatives (`audit_log` for an in-conversation tail, `verify_audit_chain` to confirm integrity first). This is a textbook when/when-not/alternative routing.

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

Deploy Server

Other Tools