Skip to main content
Glama

Verify Citation

verify_citation

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

Instructions

No-Hallucination Citation Verifier for North Macedonia (MK). Validates format and live existence of legal citations (e.g., 'Рев1.бр.123/2023 or Службен весник на РСМ бр. 20/24') against official North Macedonia 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., 'Рев1.бр.123/2023 or Службен весник на РСМ бр. 20/24').

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose that checks are against live external registries ('live existence'), hinting at remote lookups, but says nothing about failure semantics (does an unverifiable citation return a flag or an error?), latency, or rate limits — meaningful gaps for a network-dependent tool.

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 delivers the core claim and scope immediately with no filler. The marketing-style label ('No-Hallucination Citation Verifier') and the closing 'prevent AI-hallucinated citations' clause are mildly redundant with the preceding text.

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?

An output schema exists, so return values need not be explained, and there is only one simple parameter. The description covers scope, targets, and example formats; the remaining gap is what a negative verification result looks like at the tool level, which the output schema likely covers.

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?

With a single required parameter and 100% schema description coverage, the schema already defines the argument; the description's added value is confirming that ECLI/ELI identifiers and statute gazette references are in scope, aligning with the schema examples. It does not add format tolerance rules (whitespace, transliteration, abbreviations) beyond what the schema shows.

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) and resource (legal citations), names the exact registry targets (North Macedonia official registries and ECLI/ELI), and gives concrete citation format examples. It is clearly distinguishable from the sibling search_* tools, which retrieve documents rather than verify a given 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 intent ('prevent AI-hallucinated citations') implies the use case — verifying a citation you already hold — but the description never states when to prefer it over search_legislation or search_case_law, nor any exclusions or prerequisites. Usage is inferred rather than stated.

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