Skip to main content
Glama

log_audit_creator

Read-onlyIdempotent

Generate a concrete audit-logging spec for an app. POST your feature list (and optional compliance targets: soc2/hipaa/gdpr/pci) and get a full audit-event catalog (namespaced event names, actor/target/required fields, PII flags, retention), a canonical event envelope schema, a storage plan (append-only, access control, alerting), and per-framework compliance notes. A dev team can implement it directly. Deterministic, no LLM. Retention/compliance figures are common-practice defaults to verify with counsel.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "log_audit_creator"
  }
}

Input Schema

NameRequiredDescriptionDefault
stackNoOptional stack hint, e.g. "node + postgres"; adds a storage note.
featuresNoApp features, e.g. ["user login", "payments", "file upload"].
complianceNoFrameworks whose required events are overlaid on the catalog.
descriptionNoOptional free-text app description (scanned for features).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / compliance / description
      Added value: +"Frameworks whose required events are overlaid on the catalog."
    • addedInput schema / properties / stack / description
      Added value: +"Optional stack hint, e.g. \"node + postgres\"; adds a storage note."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world behavior, so the description only needs to add context, which it does: it declares "Deterministic, no LLM" and flags that "Retention/compliance figures are common-practice defaults to verify with counsel." That caveat is genuinely useful behavioral disclosure not present in any structured field, though cost/pagination/size limits of the generated spec are not addressed.

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 deliverable is front-loaded and every sentence carries information about inputs or outputs, but the middle sentence is a long comma-spliced list of output artifacts that is harder to scan than it needs to be; a light bulleted structure would improve it.

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?

With no output schema, the description carries the return-value burden and does so thoroughly by naming each output component. Combined with annotations covering the safety profile, an agent has everything needed to call it correctly, the only minor gap being what happens if the zero-required "features" argument is omitted.

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 the schema already documents stack, features, compliance, and description. The description reinforces features and the compliance enum values, but adds little syntax or constraint detail beyond the schema and never mentions the optional free-text description parameter, so the baseline 3 applies.

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 opens with a specific verb and artifact: "Generate a concrete audit-logging spec for an app." It then enumerates the exact deliverables (event catalog, envelope schema, storage plan, compliance notes), which clearly separates it from siblings like log_analyzer or mcp_tool_lint without requiring a schema read.

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 implied rather than stated: "POST your feature list … and get a full audit-event catalog" tells an agent what input to supply and who the consumer is ("a dev team can implement it directly"), but there is no explicit when-not guidance and no named alternative among the many sibling linting/analysis tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.