Skip to main content
Glama

gb_get_case

Read-onlyIdempotent

Retrieve a UK judgment from The National Archives using its neutral citation, Find Case Law URI, or opaque ID.

Instructions

Fetch a UK judgment from The National Archives' Find Case Law service.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
referenceYesa neutral citation (e.g. ``"[2026] EWHC 1698 (Admin)"``), a Find Case Law URI/path (e.g. ``"ewhc/admin/2026/1698"`` or a full ``caselaw.nationalarchives.gov.uk`` URL), or an opaque ``"d-{uuid}"`` id. Neutral citations resolve directly to a URI only for pre-April-2025 documents (``/{court}/{year}/{number}``); for later documents (opaque id), use `gb_search_case_law` first to find the ``uri``.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo
courtNo
titleNo
formatNoakn
contentNo
pdf_urlNo
byte_sizeNo
source_urlYes
dataset_noteNocaselaw.nationalarchives.gov.uk (Find Case Law, The National Archives) publishes judgments under the Open Justice Licence - a separate service from legislation.gov.uk (different host, no shared identifier scheme). Pre-April-2025 documents have a derivable URI ('/{court}/{year}/{number}'); documents from April 2025 onward use an opaque 'd-{uuid}' URI (fclid) that cannot be derived from the neutral citation alone. human_readable_citation is the neutral citation, e.g. '[2026] EWHC 1698 (Admin)'.
neutral_citationNo
human_readable_citationYes
Behavior3/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety and idempotency. Description adds the specific data source but does not elaborate on error handling, availability, or other behavioral details beyond what annotations convey.

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 main description is a single, concise sentence with no wasted words. The overall definition is well-structured with the necessary schema and annotations, making it easy to parse.

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?

Given the tool has a simple interface (1 parameter, no nested objects), the description combined with the output schema and annotations covers the essential aspects. However, it could mention what happens if the judgment is not found or confirm the output format explicitly.

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

Parameters4/5

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

The single parameter 'reference' has a detailed schema description (100% coverage) that explains multiple input formats and provides a usage hint about pre/post April 2025 documents. This adds significant meaning beyond the parameter name and type.

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 clearly states verb 'Fetch' and resource 'a UK judgment' from a specific source 'The National Archives' Find Case Law service'. It distinguishes from sibling tools like gb_get_act and gb_get_govuk_content by targeting case law specifically.

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?

Main description does not explicitly state when to use this tool vs alternatives. However, the parameter description hints that for newer documents with opaque ids, gb_search_case_law should be used first, providing indirect guidance. Lacks explicit when-to-use or when-not-to-use context.

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/gb-eli-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server