Skip to main content
Glama

Verify Citation

verify_citation

Validates Latvian legal citations against official Latvia and ECLI/ELI registries to confirm format and live existence, preventing AI-hallucinated references.

Instructions

No-Hallucination Citation Verifier for Latvia (LV). Validates format and live existence of legal citations (e.g., 'ECLI:LV:AT:2024:0101.SKC000124 or Likumi.lv') against official Latvia and ECLI/ELI registries to prevent AI-hallucinated citations.

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>"
    },
    "name": "verify_citation"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationYesCase citation, ECLI, or statute reference to verify (e.g., 'ECLI:LV:AT:2024:0101.SKC000124 or Likumi.lv').

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/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 disclose that the check is a live lookup against official Latvia and ECLI/ELI registries (i.e., network-dependent, non-deterministic availability) plus a format validation step. It does not say what happens on lookup failure, whether unverifiable registries produce a soft or hard result, or any auth/rate constraints.

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?

One sentence, front-loaded with the jurisdiction and purpose, with no filler. Minor deductions for duplicating the schema's example string and for a malformed quotation in that example, which slightly muddies readability.

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 one-parameter verification tool with an output schema, the description covers scope (Latvia only), the sources consulted, and the intent. It could say more about what 'live existence' means when a registry is unreachable, but nothing essential to invoking it correctly is missing.

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 100% for the single 'citation' parameter, so the schema already documents the type and gives the same example. The description repeats rather than extends that example and adds no format rules (e.g., accepted ECLI syntax variants). Baseline 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?

States a specific verb ('validates format and live existence') and a specific resource ('legal citations ... for Latvia') and scopes it to LV/ECLI/ELI registries. This clearly separates it from siblings like search_case_law and search_legislation, which retrieve documents rather than verify a supplied citation.

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 stated motivation ('to prevent AI-hallucinated citations') implies when to call it, but there is no explicit when/when-not guidance and no sibling is named as an alternative. An agent must infer that this is a post-generation check rather than a discovery tool.

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