Skip to main content
Glama

gb_search_case_law

Read-onlyIdempotent

Search UK case law from The National Archives' Find Case Law service. Filter by court, text, or date range to retrieve judgments with metadata.

Instructions

Search UK case law on The National Archives' Find Case Law service.

Maps to the public Atom feed at caselaw.nationalarchives.gov.uk/atom.xml (confirmed live 2026-07-06 - keyless, Open Justice Licence). A separate service from legislation.gov.uk: different host, different Atom dialect (tna: namespace).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
courtNocourt/tribunal code, e.g. ``"ewhc/admin"``, ``"ewca/civ"``, ``"uksc"``. Passed through to Find Case Law's own ``court`` query param.
limitNomax items to return (1..100).
queryNofull-text search (matches judgment text in order, per upstream docs).
to_dateNoISO 8601 date (YYYY-MM-DD), inclusive. Same client-side caveat.
from_dateNoISO 8601 date (YYYY-MM-DD), inclusive. Find Case Law's public API has no documented server-side date-range filter, so this is applied client-side against each result's ``date`` field after fetching.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNo
query_echoNo
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)'.
total_estimateYes
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint as true/false. The description adds value by confirming the service is live, keyless, and uses Open Justice Licence, and notes the Atom dialect ('tna:' namespace). 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?

The description is concise (two sentences plus a mapping note), front-loaded with the main purpose, and contains no redundant information. Every sentence adds value.

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 number of parameters (all optional) and the presence of an output schema, the description provides sufficient context about the service and its caveats (client-side date filtering). It is mostly complete, though it does not explain default behavior when no filters are applied.

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 description coverage is 100%. The description does not add new meaning beyond the schema; it only mentions the Atom feed mapping. Baseline 3 is appropriate since the schema already documents the parameters adequately.

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 clearly states 'Search UK case law' with a specific verb and resource. It distinguishes from siblings by noting it targets The National Archives' Find Case Law service and is separate from legislation.gov.uk.

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 provides context about the service (keyless, Open Justice Licence) and how it differs from legislation.gov.uk, but does not explicitly specify when to use this tool versus alternatives or when not to use it.

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