Skip to main content
Glama

legal-cite-verifier

Legal citation and quotation verifier (US case law) — Extracts US reporter citations from a brief (U.S., S. Ct., L. Ed., F., F.2d, F.3d, F.4th, F. Supp., state and regional reporters) and checks each against Harvard's Caselaw Access Project and, when the operator has configured a token, the CourtListener Citation Lookup API. Reports FOUND, MISMATCH (case name, year or circuit differs), NOT_FOUND, AMBIGUOUS, or UNCHECKED with the reason, and never mar

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": "legal-cite-verifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoBrief or memo text. Citations and their case names, court and year are extracted from it.
quotesNoQuotations to find verbatim in the cited opinion.
citationsNoCitations to check instead of, or in addition to, text.
propositionsNo
max_citationsNoDistinct reporter citations to check. Default 40.
check_propositionsNoDefault false. Runs one optional model call that may only point at a verified passage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does useful work by disclosing the two backing sources and the conditional CourtListener behavior tied to an operator token, plus the five possible verdicts. But the final clause is truncated ('and never mar'), so the one promise about its most important behavioral guarantee — presumably never marking something verified without support — is unreadable, and there is no mention of latency, cost, rate limits, or what an empty result looks like.

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 single dense sentence is front-loaded correctly — purpose, then sources, then outcomes — and carries no filler. The defect is that it is cut off mid-word at 'never mar', which both wastes the strongest clause and leaves the reader with a dangling promise.

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 six-parameter, no-annotation, no-output-schema tool, the description covers the essentials: what is extracted, where it is checked, and what verdicts come back, effectively substituting for the missing output documentation. The gaps are the truncated closing clause and the absence of any mention of the quotation-verification and proposition-checking modes that occupy three of the six parameters.

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 83%, so the baseline is 3. The description adds meaning for the text parameter by explaining that case names, court and year are extracted alongside citations, which the schema only gestures at. It says nothing about quotes, propositions, check_propositions, or max_citations, so half the surface is left entirely to the schema.

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?

States a specific verb and resource up front ('Legal citation and quotation verifier (US case law)') and then names the exact mechanism: extracting US reporter citations from a brief and checking each against Caselaw Access Project and optionally CourtListener. The enumerated reporter families and the status vocabulary make it unmistakable versus siblings like precedent-search, which retrieves authority rather than validating it.

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 by the resource ('from a brief', 'quotations to find verbatim'), so an agent can infer this is the post-drafting verification step. However, it never states when NOT to use it, never routes to a sibling for the adjacent task of finding new authority, and gives no prerequisites such as the need for well-formed reporter citations in the input.

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