Skip to main content
Glama

pk_get_decision

Read-onlyIdempotent

Fetch the complete text of a Pakistani Supreme Court judgment by providing its registry citation or dataset row index.

Instructions

Fetch one Supreme Court judgment's full text, by row index or registry citation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
case_idNoregistry file id, e.g. ``"Crl.A.93_2013.pdf"`` (used when ``row_idx`` is not given).
row_idxNo0-based dataset row index from ``pk_case_search`` (preferred).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
case_idNo
contentNo
eli_uriNo
row_idxYes
eli_noteNoPakistan has not deployed ELI. For statutes, eli_uri is the canonical Ministry of Law and Justice PDF URL (https://pakistancode.gov.pk/pdffiles/{law_id}); for judgments it is the HuggingFace dataset row URI. Stable and resolvable, never invented.
byte_sizeNo
truncatedNo
source_urlNo
dataset_noteNoCorpus-based connector: judgments come from the Ibtehaj10/supreme-court-of-pak-judgments dataset on HuggingFace (1,414 Supreme Court of Pakistan judgments, full text, MIT), a static snapshot from 2024-07-26 covering a SUBSET of the Court's output - absence of a judgment here does not mean it does not exist.
human_readable_citationNo
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is clear. The description adds that it fetches the 'full text', which is a behavioral detail not fully covered by annotations. There is no contradiction.

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?

Single, front-loaded sentence with no wasted words. Efficiently conveys the tool's action, resource, and input options.

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?

For a simple fetch tool with complete schema annotations (100% coverage) and an output schema, the description is sufficiently complete. It clarifies the input options and the result ('full text'), meeting all needs for correct invocation.

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?

Schema coverage is 100% with detailed descriptions for both parameters. The description only summarizes the input methods ('by row index or registry citation'), adding marginal value beyond the schema. Baseline 3 is appropriate.

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 uses specific verb 'Fetch' and clearly identifies the resource as 'one Supreme Court judgment's full text'. It distinguishes from siblings by specifying the input methods (row index or registry citation), making the tool's purpose unambiguous.

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

Usage Guidelines4/5

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

The description states the tool is used to fetch a judgment by row index or citation, implying it is the appropriate tool when you have one of these identifiers. It does not explicitly exclude scenarios or name alternatives, but the context from sibling tools (e.g., pk_case_search for searching) provides clarity.

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