Skip to main content
Glama

WritersLogic business agents

audit-public-record

OnRecord statutory clock & redaction auditor — Audits an agency's public-records response and leads with a decision (late, redaction problems, incomplete, pending or no violation found). Computes the statutory response deadline and days late (California CPRA, with the court-day calendar and § 7922.535 extension rules), flags redactions without an exemption citation, passages redacted in one document but readable in another, referenced attachme

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "jurisdiction": "<jurisdiction>",
      "requestDate": "<requestDate>",
      "documents": "<documents>"
    },
    "name": "audit-public-record"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfDateNoObservation date when responseDate is omitted; defaults to today (UTC).
documentsYes
agencyNameNoAgency that received the request; fills the follow-up letter.
requestDateYesDate the agency received the request (YYYY-MM-DD or RFC 3339; read in the offset written).
jurisdictionYesOnRecord jurisdiction code. Only "CA_CPRA" (alias "US-CA") has a statute table; any other value returns clock "unknown_jurisdiction" while document checks still run.
responseDateNoDate of the agency's determination/response. Omit if none yet.
requesterNameNoYour name, for the follow-up letter signature.
extensionNoticesNo
gapThresholdDaysNoReport gaps between dated events longer than this (default 30).
requestReferenceNoThe agency's request or tracking number, for the follow-up letter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does reasonably well: it says the tool leads with a decision, computes a statutory deadline and days late using a court-day calendar and § 7922.535 extension rules, and flags uncited redactions and cross-document redaction inconsistencies. It falls short only because the text is cut off mid-sentence ('referenced attachme'), so the last class of checks and any limits or performance characteristics are never disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead is well front-loaded — the decision-oriented purpose and outcomes come first, which is the right ordering. However, the text terminates mid-word, leaving a dangling clause and an incomplete list of flags, which is a structural defect rather than mere length.

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?

For a 10-parameter, no-output-schema tool, the description covers the decision outputs and the statutory computation logic well enough for an agent to call it correctly. The dangling truncation and the absence of any note on jurisdiction fallback (only in the schema) leave a small gap, but nothing essential to 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 80%, so the schema already documents most inputs (dates, jurisdiction code, extensionNotice reason enum values, thresholds). The description adds only statute-level context (California CPRA, court-day calendar, extension rules) and does not explain the roles of documents, extensionNotices, or gapThresholdDays beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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-resource phrase ('Audits an agency's public-records response') and enumerates the decision outcomes it produces (late, redaction problems, incomplete, pending, no violation found). It is clearly distinguishable from sibling auditors like audit-prose-forensics or citation-audit, though it never names an alternative explicitly.

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: the tool is for auditing an agency's public-records response under California CPRA. There is no explicit when-to-use/when-not guidance, no mention of prerequisites (e.g., needing the request date), and no routing to or away from any sibling tool.

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.

Resources