Skip to main content
Glama
Liechtenstein Legal Research MCP Server

Liechtenstein Legal Research MCP Server

by jurisatlas

Verify Citation

verify_citation

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

Instructions

No-Hallucination Citation Verifier for Liechtenstein (LI). Validates format and live existence of legal citations (e.g., 'LES 2024, 15 or LGBl. 2024 Nr. 10') against official Liechtenstein 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., 'LES 2024, 15 or LGBl. 2024 Nr. 10').

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 disclosure burden. It usefully reveals that verification queries official Liechtenstein and ECLI/ELI registries (i.e., a live network lookup, not a local format check), but says nothing about failure behavior, latency/rate limits, or what an unverifiable vs. malformed citation yields.

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?

A single front-loaded sentence that names the tool's purpose before the registry detail. Slightly redundant in restating the title ('Citation Verifier') and packing two ideas (format vs. existence) into one clause, but nothing extraneous.

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 single-parameter tool with a full input schema and an output schema, the description covers jurisdiction, source registries, and intent. The main residual gap is how partial or ambiguous citations are handled, which matters for a verifier but is a minor omission here.

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?

Only one parameter, and schema description coverage is 100%, so the schema already documents it. The description's examples of acceptable citation forms add modest meaning beyond the schema's identical example, so 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 resource ('legal citations' for Liechtenstein), plus concrete citation examples ('LES 2024, 15', 'LGBl. 2024 Nr. 10'). This is clearly distinct from the sibling search_* and get_* tools, which retrieve documents rather than verify a reference.

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 phrase 'to prevent AI-hallucinated citations' implies the use case (checking a reference before relying on it), but there is no explicit when-to-use, when-not-to-use, or named alternative such as search_legislation for finding citations you don't yet have. Guidance is inferable but not stated.

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