Skip to main content
Glama

insc.one — INSC.1 Citation Layer

audit_brief

Audit a brief, petition, or opponent argument for citation accuracy and Article 141 binding-precedent validity. Extracts every citation and verifies current treatment, flagging overruled authorities.

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": {
      "text": "<text>"
    },
    "name": "audit_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe legal text containing citations to audit.
focus_issueNoOptional legal topic to prioritize.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / focus_issue / description
      Previous value: -"Optional legal topic to prioritize in the tactical analysis."New value: +"Optional legal topic to prioritize."
    • changedInput schema / properties / text / description
      Previous value: -"The brief, petition excerpt, opponent arguments, or paragraph containing legal citations to audit."New value: +"The legal text containing citations to audit."
  2. Changed2 schema fields changed
    • changedInput schema / properties / focus_issue / description
      Previous value: -"Optional legal topic to prioritize."New value: +"Optional legal topic to prioritize in the tactical analysis."
    • changedInput schema / properties / text / description
      Previous value: -"The legal text containing citations to audit."New value: +"The brief, petition excerpt, opponent arguments, or paragraph containing legal citations to audit."
  3. Changed2 schema fields changed
    • changedInput schema / properties / focus_issue / description
      Previous value: -"Optional legal topic to prioritize in the tactical analysis."New value: +"Optional legal topic to prioritize."
    • changedInput schema / properties / text / description
      Previous value: -"The brief, petition excerpt, opponent arguments, or paragraph containing legal citations to audit."New value: +"The legal text containing citations to audit."
  4. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the internal behavior (extraction of every citation, verification of current treatment, flagging of overruled authorities), which implies a read-only analytical operation, but says nothing about cost/latency for long briefs, permissions, or the shape of the returned results.

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?

Two tight sentences: the first front-loads what is audited and against what standard, the second explains the mechanism. Every clause carries information; nothing is padding, though the phrasing is dense with domain jargon.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description should do more to describe the deliverable — whether results come back as a per-citation report, a flat flag list, or a summary verdict. It conveys the conceptual return ('flagging overruled authorities') but not enough for an agent to anticipate the response structure or its likely cost on a full brief.

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 both parameters are already documented, giving a baseline of 3. The description reinforces that the input is a full legal document containing citations, but adds no detail on how 'focus_issue' changes prioritization or how the audit output is filtered by it.

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?

States a specific verb ('Audit') and a specific resource ('brief, petition, or opponent argument') plus the two dimensions checked: citation accuracy and Article 141 binding-precedent validity, with a concrete outcome ('flagging overruled authorities'). It is clear what the tool does, though it never distinguishes itself explicitly from siblings like check_treatment or check_cross_citations, which appear to cover parts of the same ground.

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?

The wording ('Audit a brief... Extracts every citation') implies this is a whole-document batch audit rather than a single-citation lookup, which is useful context for choosing against resolve_citation or format_citation. However, there is no explicit when-to-use/when-not-to-use statement and no named alternative, so the routing decision is left to inference.

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