Skip to main content
Glama

Verify Citation

verify_citation

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

Instructions

No-Hallucination Citation Verifier for Albania (AL). Validates format and live existence of legal citations (e.g., 'Vendimi Nr. 123/2024 or Fletorja Zyrtare Nr. 15/2024') against official Albania 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., 'Vendimi Nr. 123/2024 or Fletorja Zyrtare Nr. 15/2024').

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/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 meaningful behavior beyond the name: validation covers both syntax and 'live existence' against external registries, implying a network lookup and dependence on registry availability. It does not say what happens on lookup failure, whether unverified results are distinguished from invalid ones, or whether any auth/rate limits apply.

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 tool's purpose and followed by the concrete scope and rationale. Slight marketing framing ('No-Hallucination Citation Verifier') is decorative but costs little, and nothing is redundant.

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 a full schema, an output schema covering return values, and clear jurisdiction scope, the description is nearly sufficient. The main remaining gap is failure behavior for citations that cannot be resolved, which matters for a verification tool whose verdict drives downstream trust.

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?

There is a single parameter with 100% schema description coverage, so the baseline is 3. The description's example ('Vendimi Nr. 123/2024 or Fletorja Zyrtare Nr. 15/2024') largely duplicates the schema's own example and adds no new format rules, accepted variants, or normalization guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb+resource pair: it 'validates format and live existence of legal citations' against official Albania and ECLI/ELI registries. That is clearly distinct from the sibling search_* and get_* tools, but the description never explicitly contrasts itself with them, so the differentiation is implicit rather than stated.

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?

Usage is only implied: an agent can infer it should call this before relying on or emitting a citation, but the description gives no explicit trigger conditions, no when-not-to-use cases, and no named alternative (e.g., search_legislation for finding a citation you don't have yet). The Albania-only scope is the one useful boundary it does convey.

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