Skip to main content
Glama

report_corpus_issue

Flag apparent defects in stored North Dakota legal text—such as garbled words, missing passages, or wrong citations—so a person can review the exact version served.

Instructions

Report an apparent defect in this corpus's text so a person can check it.

Use it when an authority you retrieved from this server looks wrong: garbled or OCR-mangled words, a paragraph or footnote missing or in the wrong place, a syllabus or caption that does not belong, a statute or rule version that cannot be the one in force on the date you asked for, a citation that resolves to the wrong document, a quotation the court made that this server's text cannot match. Do NOT use it for disagreement with what the law says, for questions, or for anything but the fidelity of the stored text to the official source.

The report is recorded with the canonical citation and the exact version this server serves today, and is read by a person; nothing changes automatically. You get a receipt with a report id.

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": {
      "citation": "<citation>",
      "issue": "<issue>"
    },
    "name": "report_corpus_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueYesOne to three sentences: what looks wrong, where in the text (paragraph / subsection), and why you think so.
citationYesThe authority whose text looks wrong (opinion, N.D.C.C. section, rule, constitutional provision, admin-code section) — as precise as you can (include as_of_date context in `issue`).
source_urlNoWhere the expected text can be seen (optional).
text_expectedNoThe passage as the official source has it, if you checked (optional, up to 4,000 characters).
text_as_servedNoThe passage as this server returned it (optional, up to 4,000 characters).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.0.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so: it discloses that the report is recorded with the canonical citation and the exact version served today, that it is read by a person, that 'nothing changes automatically,' and that the caller receives a receipt with a report id. That covers the side-effect profile, the human-in-the-loop consequence, and the immediate response, none of which is derivable from the schema.

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 and front-loaded: purpose first, then acceptance criteria, then exclusions, then what happens to the report. The enumerated defect types run long and overlap somewhat (OCR mangling vs. misplaced paragraphs), but each clause carries decision-relevant information rather than filler.

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?

An output schema exists, so the description needn't explain the return payload — and it still names the receipt and report id, which is the part an agent needs to act on. Combined with the disclosed side effects and the explicit exclusion list, nothing material is missing for correct invocation of this write-adjacent reporting tool.

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 every parameter is already documented in the input schema (including that `issue` should carry as_of_date context and that expected/served passages are capped at 4,000 characters). The description reinforces the citation/version framing but adds no syntax, format, or constraint detail beyond what the schema states, so the baseline of 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 opening sentence states a specific verb and resource: 'Report an apparent defect in this corpus's text so a person can check it.' The object of the report is scoped to the stored text's fidelity to the official source, which cleanly separates it from every retrieval/graph sibling in the catalog.

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?

Gives an explicit positive trigger list (garbled or OCR-mangled words, misplaced paragraphs or footnotes, stray syllabus, wrong statute version for the requested date, misresolving citation, unmatchable quotation) and an explicit negative list ('Do NOT use it for disagreement with what the law says, for questions, or for anything but the fidelity of the stored text'). The use/do-not-use boundary is stated outright rather than inferred.

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