Skip to main content
Glama
Cyprus Legal Research MCP Server

Cyprus Legal Research MCP Server

by jurisatlas

Verify Citation

verify_citation

Validates the format and live existence of Cyprus legal citations against official ECLI/ELI and statute registries to prevent AI-hallucinated references.

Instructions

No-Hallucination Citation Verifier for Cyprus (CY). Validates format and live existence of legal citations (e.g., 'ECLI:CY:AD:2024:10 or Cap. 149') against official Cyprus 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:CY:AD:2024:10 or Cap. 149').

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: two distinct checks (format validation and 'live existence') against external official Cyprus and ECLI/ELI registries, which signals network dependency and possible latency. It does not mention failure modes, rate limits, or what an unresolvable citation yields, but the presence of an output schema covers the response shape.

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 tight sentence with the jurisdiction and examples front-loaded; nothing is redundant. The leading label 'No-Hallucination Citation Verifier for Cyprus (CY)' is slightly promotional but also serves as a scannable scope marker.

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 an output schema, the description supplies the essentials: jurisdiction, accepted citation types, and that verification goes to live registries. The only material gap is what a failed or inconclusive verification looks like procedurally (e.g., registry unavailability).

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% and the single 'citation' parameter is fully documented, so the schema already does the work. The description repeats the same example strings without adding format rules, accepted prefixes, or normalization guidance beyond 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?

The description uses a specific verb+resource ('Validates ... legal citations') and names the exact scope: Cyprus (CY), with concrete example formats ('ECLI:CY:AD:2024:10 or Cap. 149'). It is clearly distinguishable from siblings like search_case_law and search_legislation, which retrieve documents rather than validate an already-known 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 goal ('to prevent AI-hallucinated citations') implies the use case of checking a citation before relying on it, but there is no explicit when-to-use/when-not or routing to alternatives. An agent is left to infer that search_case_law is for discovery and verify_citation for validation.

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