Skip to main content
Glama

caselaw_search_questions

Read-onlyIdempotent

Find judgments by the QUESTION they settle, rather than by words they contain.

Every judgment summary on this corpus records the questions that judgment actually decides — e.g.
"Does delay in lodging the FIR by itself entitle the accused to bail?" This searches those
questions, so it matches the shape a legal problem arrives in rather than the vocabulary a
1987 bench happened to use.

COVERAGE IS PARTIAL: only some judgments have a summary with questions yet (the response's
`coverage_note` gives the current live ratio, which keeps growing). An empty result means no
*summarised* judgment matched — it does NOT mean no such judgment exists. Fall back to
caselaw_search, which covers the whole corpus.

The questions are prepared from the judgment text. They are a finding aid, not a
holding: cite the judgment, never the question. Pass an id to caselaw_get_case to read it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
courtNoOnly this court, e.g. 'Supreme Court' or 'Lahore High Court'
judgeNoOnly judgments where this judge sat on the bench (spelling-tolerant, e.g. 'Mansoor Ali Shah')
limitNo
queryYesThe legal question or its subject, in the words a judgment would use — 'delay in lodging FIR', 'concurrent findings of fact', 'pre-arrest bail murder'
offsetNo
year_toNoLatest year (inclusive)
year_fromNoEarliest year (inclusive)
response_formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / judge
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 100,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Only judgments where this judge sat on the bench (spelling-tolerant, e.g. 'Mansoor Ali Shah')",
      +  "title": "Judge"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / court
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 100,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Only this court, e.g. 'Supreme Court' or 'Lahore High Court'",
      +  "title": "Court"
      +}
    • addedInput schema / properties / year_from
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 2100,
      +      "minimum": 1900,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Earliest year (inclusive)",
      +  "title": "Year From"
      +}
    • addedInput schema / properties / year_to
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 2100,
      +      "minimum": 1900,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Latest year (inclusive)",
      +  "title": "Year To"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the lower bar applies. Beyond that, the description discloses a genuinely non-obvious behavior: partial coverage with a live `coverage_note` ratio, the misleading-empty-result caveat, and the 'finding aid, not a holding' citation rule. It could still say more about ranking or result ordering, but this is well above baseline.

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?

Front-loaded with the core differentiator, and every paragraph carries distinct information (scope, coverage caveat, citation rule, follow-up). It runs slightly long across four sections, but no sentence is filler.

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?

An output schema exists, so return values need not be explained, and the description still supplies the coverage caveat the schema cannot. Combined with usage routing and the follow-up call, an agent has everything needed to invoke and interpret this correctly.

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 63%, and the schema itself already documents court, judge, query, and the year filters. The description's only added parameter value is conceptual framing for `query` (legal question phrasing), while limit, offset, and response_format remain undocumented in both places. Baseline 3 for a mid-coverage schema where the description does not materially extend per-parameter meaning.

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?

States a precise verb+resource distinction ('find judgments by the QUESTION they settle, rather than by words they contain') and defines the corpus object being searched (judgment summaries recording decided questions). This cleanly separates it from the sibling caselaw_search that matches on vocabulary.

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?

Explicitly gives when-to-use ('matches the shape a legal problem arrives in'), when-not (coverage is partial, empty result does not mean no such judgment exists), and the named alternative to fall back to (caselaw_search). It also routes the agent onward to caselaw_get_case for reading the id.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources