Skip to main content
Glama
paulieb89

UK Legal Research MCP Server

Get Case Citation Network

citations_network
Read-onlyIdempotent

Extract and group all OSCOLA citations from a judgment XML by type, deduplicated and sorted, for authority-network analysis.

Instructions

USE THIS TOOL WHEN you have a judgment slug and want to map every citation it makes — cases cited, legislation referenced, SIs, retained EU law.

Fetches the judgment XML from TNA and parses all OSCOLA citations within. Returns citations grouped by type, deduplicated and sorted. AFTER calling, pass any individual citation through citations_resolve to confirm it resolves and to retrieve its canonical URL.

Useful for authority-network analysis (what did this judgment rely on?) and for surfacing the legislative landscape a case sits inside.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
case_uriYesTNA judgment URI slug, e.g. 'uksc/2024/12' or 'ewca/civ/2023/450'. Use the 'uri' field from case_law_search results — not the full URL. Do not include the 'https://caselaw.nationalarchives.gov.uk/' prefix.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
case_uriYesThe judgment URI that was fetched and parsed
neutral_citationsNoNeutral citations referenced, e.g. '[2020] UKSC 14'
legislation_refsNoLegislation section references, e.g. 's.47 Companies Act 2006'
si_refsNoStatutory Instrument references, e.g. 'SI 2018/1234'
eu_refsNoRetained EU law references, e.g. 'Regulation (EU) 2016/679'
law_report_refsNoLaw report citations, e.g. '[2020] 1 WLR 100'
total_citationsYesSum of all de-duplicated citations across every bucket
Behavior5/5

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

Annotations declare readOnlyHint=true and idempotentHint=true, and the description adds context: it fetches judgment XML from TNA, parses OSCOLA citations, and returns results grouped, deduplicated, and sorted. This goes beyond annotations and provides full behavioral transparency.

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 well-structured with a clear call-to-action at the start, followed by technical details and usage guidance. Every sentence adds value, and there is no redundancy.

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 that an output schema exists (context signal: 'Has output schema: true'), the description does not need to detail return values. It covers all necessary aspects: what, when, how, and follow-up steps. The tool is simple (one param) and the description is complete.

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?

The single parameter 'case_uri' has a detailed description in the schema (100% coverage) that goes beyond basic type: it provides format examples, source advice ('use the 'uri' field from case_law_search results'), and what to exclude. This adds significant 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?

The description clearly states the tool's purpose: mapping all citations (cases, legislation, SIs, retained EU law) from a judgment slug. It uses specific verbs like 'map' and 'fetch', and the title reinforces this. The description also distinguishes it from sibling tools like citations_resolve.

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?

The description explicitly says when to use this tool ('when you have a judgment slug and want to map every citation it makes') and provides post-call guidance ('AFTER calling, pass any individual citation through citations_resolve'). This clarifies usage order and alternatives.

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