Skip to main content
Glama

Verify Citation

verify_citation

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

Instructions

No-Hallucination Citation Verifier for Montenegro (ME). Validates format and live existence of legal citations (e.g., 'Rev.br. 123/24 or Službeni list CG br. 15/2024') against official Montenegro 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., 'Rev.br. 123/24 or Službeni list CG br. 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, and it does disclose that this is a live external lookup against official Montenegro and ECLI/ELI registries plus a format check. It does not state what happens when a registry is unreachable, whether a failed verification is distinguished from an unknown registry, or any latency/rate considerations. An output schema exists, so return values needn't be explained here.

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?

Two sentences, front-loaded with the verifier role and jurisdiction before the mechanism. Slightly dense with stacked qualifiers ('official Montenegro and ECLI/ELI registries'), but no sentence is wasted.

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 purpose, jurisdiction, and verification sources adequately. The remaining gaps (failure modes, registry availability, whether non-Montenegro citations are rejected) are real but minor at this complexity level.

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 required parameter with 100% schema description coverage, and the schema already supplies the same example citation formats. The description reinforces the accepted citation types ('Rev.br. 123/24 or Službeni list CG br. 15/2024') but adds no constraints beyond the schema, so baseline 3 applies.

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?

States a specific verb ('Validates format and live existence') against a specific resource (legal citations) with an explicit jurisdiction scope (Montenegro/ME) and named registries. It is clearly distinguishable from the sibling search_* tools by being a verifier rather than a retriever, though it never names those siblings directly.

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 ('prevent AI-hallucinated citations') implies the situation in which to use it, and the contrast with search tools is inferable from the word 'validates'. However, there is no explicit when-to-use/when-not-to-use statement, no mention of what to do if verification fails, and no named alternative such as search_case_law for finding a citation you don't yet have.

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