Skip to main content
Glama

Citation Safe Verifier

by com.citationsafe

Check whether a single case citation is real

is_this_case_real
Read-only

Deterministic existence check (Layer 1 only, no LLM) for one legal citation against CourtListener's primary-source database. Answers the single question "is this case real" for one citation — for multi-citation quote-checked verdicts across a whole brief, use verify_brief instead. Free tier: 5 checks/day per IP, no key required. For unlimited access, pass an API key as "Authorization: Bearer " (contact support@citationsafe.com to request one).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
citationYesA single citation, e.g. "410 U.S. 113" or "Roe v. Wade, 410 U.S. 113 (1973)"

TDQS

A4.9/5.0
Behavior5/5

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

Description adds deterministic, Layer 1, no LLM, and database source info beyond annotations which only say readOnlyHint. Also discloses rate limits and authentication requirements.

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

Conciseness5/5

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

Concise and well-structured: purpose first, then differentiation, then usage limits, then authentication. No wasted words.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers all needed aspects: what it does, when to use, rate limits, and authentication. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema already describes the citation parameter with 100% coverage. Description adds concrete examples like '410 U.S. 113' and 'Roe v. Wade, 410 U.S. 113 (1973)', providing useful formatting guidance.

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?

Description clearly states the tool checks if a single legal citation is real, using a deterministic no-LLM method against CourtListener. It distinguishes from siblings like verify_brief which handles multiple citations.

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?

Explicitly says when to use this tool (single citation) vs when to use verify_brief (multi-citation brief). Also covers free tier limits and how to get unlimited access with an API key.

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

All Citation Safe Verifier toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct operation: citation verification on pasted text, on document URLs, batch verification, retrieving past results, and searching sanctions. No overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with underscores (e.g., verify_citation, batch_verify_citations, search_sanctions), making the tool set predictable.

Tool Count5/5

Five tools is well-scoped for citation verification: single, document, batch, retrieval, and sanctions search. No redundant or excessive tools.

Completeness4/5

Core verification workflows (single, document, batch, retrieval) are covered. A listing endpoint for all verifications is missing but not critical for typical use.

Resources