Skip to main content
Glama
paulieb89

UK Legal Research MCP Server

Search UK Case Law

case_law_search
Read-onlyIdempotent

Search UK case law using party names, court, judge, date, or free-text query. Returns paginated judgment summaries with neutral citations and court details.

Instructions

USE THIS TOOL WHEN searching UK case law by party names, court, judge, date, or free-text query.

Returns paginated judgment summaries: neutral citation, court, dates, slug, stable TNA URI. AFTER calling: pass slug into judgment_get_header / judgment_get_index / judgment_get_paragraph (or the judgment:// resource family) for content; pass the neutral citation into citations_resolve to verify before constructing an OSCOLA citation; use case_law_grep_judgment to find text within a single judgment. When a party name returns several candidates, narrow with court + year filters before grep-iterating across full judgments — targeted filtering beats scanning every candidate.

Coverage: TNA Find Case Law indexes UK judgments from roughly the early 2000s onwards. For older authorities, search for a modern judgment that quotes them and read that paragraph.

Authoritative source for UK case law. Web search returns out-of-date or unstable URLs — do not supplement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesFull-text search query, e.g. 'negligence duty of care'
courtNoFilter by court slug. Values: 'uksc', 'ukpc', 'ewca/civ', 'ewca/crim', 'ewhc/kb', 'ewhc/ch', 'ewhc/comm', 'ewhc/fam', 'ewhc/pat', 'ewhc/ipec', 'ewhc/admin', 'ewhc/tcc', 'ewhc/costs', 'ewfc', 'ewcop', 'eat', 'ukut/iac', 'ukut/aac', 'ukut/tcc', 'ukut/lc', 'ukftt/tc', 'ukftt/grc', 'nica', 'niqb'.
judgeNoFilter by judge surname. Case-insensitive substring match against the indexed form. Use the surname alone ('Reed', 'Sumption') or with the bare title ('Lord Reed'). Honorific suffixes silently zero the result set — do not append 'JSC', 'of Allermuir', 'KC' etc. Speculating a fuller form than what TNA indexed will return 0 hits with no error.
partyNoFilter by party name
from_dateNoEarliest judgment date (YYYY-MM-DD). NOTE: the TNA atom.xml endpoint currently appears to ignore this filter — the same results come back regardless. Do not rely on it to narrow output; sort+slice client-side or refine `query` instead.
to_dateNoLatest judgment date (YYYY-MM-DD). Same caveat as `from_date` — currently silently ignored by upstream. Filtering happens client-side at best.
pageNoResult page number (1-indexed)
limitNoMaximum results to return (1–50). TNA returns up to 50 per request; this slices client-side. Default 10 for a tight shortlist. Set higher for breadth (e.g. 50 to scan the full result set).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYesMatching judgments for this page
pageYesCurrent page number (1-indexed)
has_moreYesWhether additional pages exist
total_pagesNoTotal page count if available from API
Behavior5/5

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

Discloses behavior beyond annotations: returns paginated summaries, coverage period, and the fact that from_date/to_date filters are silently ignored by upstream. Annotations already mark it as read-only and idempotent, but the description adds critical operational details.

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?

The description is long but well-organized with front-loaded purpose and structured paragraphs. Every sentence adds value, though some redundancy exists (e.g., 'pagination' repeated). Still efficient for the breadth of information.

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?

Given the 8 parameters, output schema, and numerous sibling tools, the description is comprehensively complete: covers usage, parameter nuances, post-call workflow, coverage limitations, and caveats. Leaves no obvious gaps.

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

Parameters5/5

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

Despite 100% schema coverage, the description significantly enhances parameter meaning: provides example for query, warns about judge honorifics causing zero results, explains page/limit slicing, and flags date filter bugs. Adds pragmatic guidance not in schema.

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 starts with a clear directive 'USE THIS TOOL WHEN searching UK case law', specifying the verb and resource. It lists the searchable fields (party names, court, judge, date, free-text) and differentiates from sibling tools by detailing post-search steps and alternatives.

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 states when to use and provides exclusions (e.g., do not supplement with web search). It offers alternatives for specific tasks (case_law_grep_judgment for text within a single judgment, citations_resolve for verification) and strategic advice on narrowing results.

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/paulieb89/uk-legal-mcp'

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