Skip to main content
Glama

Meta Council

by com.meta-council
OverviewDiscussionsAdmin

Audit Export

audit_export
Read-onlyIdempotent

Export this workspace's own agent-action audit trail as structured events, oldest first, for loading into a SIEM. Each event carries what triggered the action, which identity authorized it, which resource was touched, the outcome, and the error state. Metadata only -- no prompt text, document content, tool arguments, or model output is ever returned. Filter by date range and event action; page forward with the cursor each response returns. Covers a documented subset of platform activity rather than every action: see docs/WORKSPACE_AUDIT_EXPORT.md, and note that the coverage block on every response lists exactly which actions are exportable and which are not. Requires authentication and the audit:read scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoEvents per page. Defaults to 100, maximum 500.
sinceNoISO-8601 lower bound, inclusive, for example 2026-08-01T00:00:00Z. Omit for no lower bound.
untilNoISO-8601 upper bound, inclusive. Omit for no upper bound.
actionNoExact event action to filter to, for example mcp.tool_call. Omit to return every action this workspace can export.
after_idNoResume cursor. Pass the next_cursor from the previous page to continue without re-reading it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "text": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "text"
-  ],
-  "type": "object"
-}New value: +null
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Adds significant disclosure beyond the annotations: explicitly states that no prompt text, document content, tool arguments, or model output is ever returned; requires authentication and the audit:read scope; describes ordering (oldest first), pagination via cursor, and the coverage block on every response. Annotations already cover read-only, idempotent, and non-destructive hints, and the description complements these with concrete behavioral details.

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 but every sentence adds value: purpose, event contents, exclusions, filtering, pagination, coverage caveat, and authentication. It is well-structured with the core purpose front-loaded. It is a bit long but warranted given the tool's complexity.

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?

For a 5-parameter tool with no output schema, the description is remarkably complete: it explains what each event carries, how to paginate, what is excluded, coverage limits, and authentication requirements. It even points to external docs for the full action list. Nothing essential for correct invocation is missing.

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 all parameters are documented in the schema. The description reinforces the purpose of since/until/action and the after_id cursor, but does not add new semantics beyond what the schema already provides. The baseline of 3 applies because the schema does the heavy lifting.

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 verb (export) and resource (workspace's own agent-action audit trail), and specifies the use case (loading into a SIEM). It differentiates from the sibling account_export by scoping to workspace and explicitly stating what is excluded (metadata only, no prompt text, etc.).

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 clear context for when to use: for SIEM loading, with filtering by date and action, and pagination. It notes that it covers a documented subset of platform activity rather than every action, which guides usage away from full-coverage expectations. It points to docs/WORKSPACE_AUDIT_EXPORT.md for details. It does not explicitly name an alternative tool, but the subset caveat serves as an implicit exclusion.

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

All Meta Council toolsInspect
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.

Resources