Skip to main content
Glama

Citation Safe Verifier

by com.citationsafe

Verify every citation in a brief or excerpt

verify_brief
Read-only

Runs existence (Layer 1) and quote-match (Layer 2) checks — both deterministic, no LLM — on every citation found in the given text and returns one verdict per citation. The multi-citation counterpart to is_this_case_real. Proposition support (Layer 3) is not included on this free/API-key surface; sign in at citationsafe.com for full 3-layer verification via verify_citation. Free tier: 5 checks/day per IP (one verify_brief call = one check, regardless of how many citations the text contains); an API key bypasses the daily cap.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesRaw text (brief excerpt, motion, memo) containing one or more legal citations

TDQS

A5/5.0
Behavior5/5

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

Annotations provide readOnlyHint. Description adds that checks are deterministic and no LLM used, that Layer 3 is excluded, and clarifies free tier caps. No contradictions.

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?

Three sentences: core function with layers, limitation and alternative, and free tier info. No wasted words, well-structured.

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?

For a tool with one parameter and no output schema, the description covers functionality, limitations, tier restrictions, and relation to siblings. Enough for an agent to select and invoke correctly.

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

Parameters5/5

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

Schema has 100% coverage for single param 'text' with description. Description adds that text can be a brief excerpt or motion, reminds of max length, and explains that one call counts as one check regardless of citation count.

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?

Clearly states the tool runs deterministic existence and quote-match checks on every citation in a brief/excerpt, returning one verdict per citation. Distinguishes itself from sibling 'is_this_case_real' as the multi-citation counterpart.

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 tells when to use (verifying citations in brief/excerpt), when not (for proposition support/Layer 3), and alternatives (verify_citation with sign-in). Also explains free tier limits and API key bypass.

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