Skip to main content
Glama

Most-cited judgments

caselaw_most_cited
Read-onlyIdempotent

List the most-cited (landmark) judgments in the corpus, ranked by how many other cases cite them. A good entry point for the leading authorities on Pakistani law.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "caselaw_most_cited"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
response_formatNomarkdown

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds genuinely useful behavior beyond that: results are ordered by incoming citation count and represent 'landmark' authorities. It does not state whether ranking scores are returned, how ties are broken, or that the result set is paginated, which are the remaining unknowns.

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?

Two sentences, front-loaded with the core action and ranking rule, then the use case. Nothing redundant for a simple read tool.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. What remains thin is the pagination story and the fact that the ranking metric is not explained quantitatively — minor gaps for a low-complexity, zero-required-parameter tool.

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 0% — all three parameters (limit, offset, response_format) carry no descriptions. The description compensates for none of them: it never explains the page size cap of 50, the offset window, or what markdown vs json returns. Names and defaults make the parameters guessable, but that is the schema's doing, not the description's.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List the most-cited (landmark) judgments in the corpus') plus the ranking criterion ('ranked by how many other cases cite them'). It doesn't contrast itself with siblings like caselaw_search or caselaw_get_citations, so the differentiation is implicit rather than explicit.

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?

'A good entry point for the leading authorities on Pakistani law' implies a discovery/browse use case, which is real guidance about when this tool fits. But there is no when-not guidance and no named alternative (e.g., use caselaw_search for keyword queries, caselaw_get_cited_by for one case's incoming citations).

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