Skip to main content
Glama

pk_verify_citations

Read-onlyIdempotent

Verifies Pakistani legal citations in text against a corpus, flagging non-existent sections and mismatched descriptions for review.

Instructions

Verify Pakistani legal citations found in a text against the corpus.

Extracts statute sections ("section 302 of the Pakistan Penal Code", "section 10A of the Pakistan Study Centres Act, 1976"), act coordinates ("Act No. XLV of 1860"), Constitution articles ("Article 184(3) of the Constitution") and Supreme Court registry citations ("Crl.A. 93/2013"), then checks each against the local corpus. A parenthetical description right after a citation is content-checked with a trigram match (mismatch = review signal). Non-existent sections come back with a range hint of what DOES exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesthe text to verify (an LLM answer, a memo, a pleading).
max_citationsNocap on citations to verify (1..30, default 15).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
gapsNo
totalYes
statusYes
summaryYes
citationsNo
dataset_noteNoVerification runs against the local corpus snapshots (statutes 2025-01-30, judgments 2024-07-26). Statute section detection reads the 'N. Heading' markers that survived OCR, so [MISSING] describes the machine-detectable text of the snapshot - treat it as a strong signal and confirm at source_url before accusing anyone. The judgment corpus is a 1,414-judgment SUBSET, so a case citation that is not found is reported as a gap, never as a hallucination. Everything the tool could not check lands in `gaps`, not in silence.
failed_countYes
warning_countYes
verified_countYes
Behavior5/5

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

Annotations declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. Description adds significant behavioral context: extracts specific citation types, checks against corpus, performs trigram content matching for parenthetical descriptions, and provides range hints for non-existent sections. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five well-structured sentences, each adding unique value. Front-loaded with main purpose. No extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (multiple citation types, trigram matching, range hints), the description is complete. Output schema exists (as per context signals), so return values need not be explained. All essential behavioral aspects are covered.

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?

Schema coverage is 100% with descriptions for both parameters. Description adds value beyond schema by explaining what types of citations are expected in 'text' and the default cap for 'max_citations', plus content-checking behavior. Provides extra meaning not present in 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?

Description clearly states the tool verifies Pakistani legal citations, lists specific citation types (statute sections, act coordinates, Constitution articles, Supreme Court registry citations) and explains the verification process. Distinguishes from sibling tools which are search-oriented.

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?

Description implies use for verifying citations in legal texts like LLM answers, memos, or pleadings, but does not explicitly state when to use vs alternatives or when not to use. Sibling tools are for searching, not verification, so guidance is implicit but not explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/matematicsolutions/pk-eli-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server