pk-eli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PK_ELI_AUDIT_DIR | No | JSONL audit log (one line per tool call) | ~/.matematic/audit |
| PK_ELI_CACHE_DIR | No | Corpus file + HTTP cache | ~/.matematic/cache/pk-eli |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pk_search_lawsA | Keyword search over Pakistan's 967 federal statutes (title-weighted ranking). |
| pk_get_lawA | Fetch the full text of one federal statute. Large statutes are truncated. |
| pk_case_searchA | Full-text search over 1,414 Supreme Court of Pakistan judgments (server-side). |
| pk_get_decisionA | Fetch one Supreme Court judgment's full text, by row index or registry citation. |
| pk_coverageA | Declare what this connector covers, how it is sourced, and what it does NOT cover. Call this before telling a user that the law "does not contain" something, and whenever a search comes back empty: the absence may be a gap in this connector rather than in the law. Every gap carries a fallback saying where to look instead. Returns:
|
| pk_verify_citationsA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool maps to a distinct operation: statute search, statute retrieval, case search, case retrieval, coverage disclosure, and citation verification. The search/get pairs are clearly separated by corpus, and pk_verify_citations has a specialized purpose that does not overlap with the plain search tools.
Most tools follow a pk_ + verb_noun pattern such as pk_search_laws and pk_get_decision, but pk_case_search reverses the order and pk_coverage is a bare noun rather than a verb phrase. The pk_ prefix provides some consistency, but the naming conventions are mixed overall.
Six tools is well-scoped for a legal research connector: two search/retrieve pairs cover the two corpora, plus coverage and citation verification add necessary meta-capabilities. Each tool earns its place and none feel redundant.
The set covers search and retrieval for both federal statutes and Supreme Court judgments, plus citation verification and explicit gap disclosure, which is strong for a read-only legal corpus. The main limitation is that large statutes are truncated with no continuation mechanism, and case retrieval relies on row index or registry citation rather than broader citation formats.