Pakistan Case Law

Cases a judgment cites

caselaw_get_citations

Read-onlyIdempotent

Walk the citation graph FORWARD: list the in-corpus cases that THIS judgment cites (the precedents it relied on). Combine with caselaw_get_cited_by to traverse precedent backward and forward until a research question is resolved.

Most useful on RECENT judgments: a 2024-25 case usually has nobody citing it yet, but its
own citation list is a curated map of the established authority on the point.

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`case_id`	Yes	Numeric judgment id
`response_format`	No		markdown

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 1, 2026
- removedInput schema / $defs
```
Removed value: -{
-  "Fmt": {
-    "enum": [
-      "markdown",
-      "json"
-    ],
-    "title": "Fmt",
-    "type": "string"
-  }
-}
```
- removedInput schema / properties / response_format / $ref
```
Removed value: -"#/$defs/Fmt"
```
- addedInput schema / properties / response_format / enum
```
Added value: +[
+  "markdown",
+  "json"
+]
```
- addedInput schema / properties / response_format / title
```
Added value: +"Response Format"
```
- addedInput schema / properties / response_format / type
```
Added value: +"string"
```
First observedSep 6, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds useful behavioral context about in-corpus scoping and forward direction, but it does not mention pagination behavior or rate limits.

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?

The description is three compact sentences, front-loaded with the core operation, followed by sibling integration and a useful recency heuristic. Every sentence earns its place and there is no filler.

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?

The output schema and annotations carry return and safety details, and the description covers direction, corpus scope, and primary usage. Pagination behavior for limit and offset is not mentioned, which is a minor gap for a list tool but does not prevent correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%: case_id is documented in the schema, while limit, offset, and response_format are not. The description refers to 'THIS judgment' but gives no semantics for pagination or response format, so it does not compensate for the low schema coverage.

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?

The description states a specific action: list the in-corpus cases that THIS judgment cites, and defines this as walking the citation graph forward. It explicitly contrasts this with caselaw_get_cited_by, so sibling differentiation is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly tells the agent to combine this tool with caselaw_get_cited_by for backward and forward graph traversal. It also gives a concrete selection heuristic: most useful on recent judgments that have no citing cases yet but do cite established authority.

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

All Pakistan Case Law tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?