Skip to main content
Glama
SSX360

matrixscroll

by SSX360
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

audit_export

Export audit bundles with verification proofs for compliance and procurement. Outputs JSON, GUAC JSONL, or evidence-pack envelopes.

Instructions

Export a compliance or procurement audit bundle with optional verification proofs.

Use when auditors need envelope bundles (JSON, GUAC JSONL, or evidence-pack).
Prefer ``verify_pr_range`` for merge-gate pass/fail on a commit range.
Prefer ``list_envelopes`` to browse hosted metadata without exporting files.

Hosted (Team+): requires SSX360_API_KEY; calls ssx360.com/api/v1/audit/export.
Local fallback: exports from git notes or on-disk envelopes when no API key.
Side effects: writes files under ``output_dir`` locally; hosted mode returns
download metadata. Returns ``{ok, bundle?, download_url?, error?}``.

Parameters:
    start_date / end_date: ISO 8601 UTC bounds (hosted filter).
    signer_id: Filter by device_id or public-key fingerprint.
    format: json, guac, or evidence-pack serialization.
    include_verification: Attach per-envelope verification replay data.
    workspace / base / head / output_dir: Local fallback range and output path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseNoLocal-only: Git ref (exclusive) when exporting from git notes or on-disk envelopes.origin/main
headNoLocal-only: Git ref (inclusive) when exporting from git notes or on-disk envelopes.HEAD
formatNoExport serialization: json (envelope bundle), guac (GUAC JSONL ingest), or evidence-pack (hosted Team+ procurement bundle with verification metadata).json
end_dateNoISO 8601 UTC upper bound for audit records (inclusive), e.g. 2026-06-30T23:59:59Z.
signer_idNoFilter export to envelopes signed by this device_id (MS-XXXX-YYYY) or Ed25519 public-key fingerprint. Empty includes all signers in scope.
workspaceNoGit repository root for local fallback export. Empty auto-detects from cwd.
output_dirNoLocal-only: directory for exported files. Relative paths resolve under the repo root..matrixscroll/audit-export
start_dateNoISO 8601 UTC lower bound for audit records (inclusive), e.g. 2026-01-01T00:00:00Z. Hosted export filters org audit history; local export filters by commit author date when available.
include_verificationNoWhen true (default), attach per-envelope verification results and trusted-key policy outcomes to the export for auditor replay without re-running Scroll Gate.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Discloses side effects (writes files locally, hosted mode returns metadata), authentication requirement (SSX360_API_KEY), and return format. Annotations indicate non-read-only and non-destructive, but description adds critical context like local vs hosted behavior.

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-structured with a clear opening sentence, usage guidance, then parameter descriptions. Could be slightly more concise, but each sentence adds value. Front-loaded with purpose.

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?

Covers all necessary context: usage scenarios, side effects, authentication, hosted vs local modes, return format, and parameter details. Output schema exists, so return info is supported. Very thorough.

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%, but description adds meaningful context beyond schema: date format (ISO 8601 UTC), signer_id types (device_id or fingerprint), format meanings, and include_verification purpose. Slightly above baseline 3.

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 explicitly states 'Export a compliance or procurement audit bundle with optional verification proofs,' using a specific verb and resource. It distinguishes from sibling tools by mentioning alternative use cases.

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?

Provides explicit guidance: 'Use when auditors need envelope bundles...', and directs to 'verify_pr_range' for merge-gate pass/fail and 'list_envelopes' for browsing, clearly indicating when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SSX360/matrixscroll'

If you have feedback or need assistance with the MCP directory API, please join our Discord server