Skip to main content
Glama
paulieb89

UK Legal Research MCP Server

Resolve Single OSCOLA Citation

citations_resolve
Read-onlyIdempotent

Resolve a UK legal citation to confirm it points to a real document, returning parsed fields and a URL. Use before constructing an OSCOLA citation to avoid fabrication.

Instructions

USE THIS TOOL BEFORE constructing an OSCOLA citation string from known fields, OR when you have a citation and want to confirm it points at a real document.

Parses + resolves a single citation (neutral citation, SI, legislation section, retained EU law) and returns the parsed fields plus a resolved_url. Raises ValueError if nothing recognisable is found.

Formatting a citation from "known" fields (year, court, number) without prior resolution is the most common citation-fabrication route — the formatter accepts whatever you give it and produces plausible-looking output for invented inputs. If this tool raises or returns no resolved_url, do NOT manufacture a citation — surface the failure and ask the user for the source URL or better identifying details.

Authoritative source for UK legal-citation resolution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYesCitationsResolveInput.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawYesOriginal citation text as found in the source
typeYesClassification of the citation type
yearNoYear component of the citation
courtNoCourt code: UKSC, UKPC, EWCA Civ, EWCA Crim, EWHC (KB), EWHC (Ch), EWHC (Comm), EWHC (Fam), EWHC (Pat), EWHC (IPEC), UKUT (IAC), UKUT (TCC), UKUT (AAC), UKUT (LC), EAT, UKFTT (TC), UKFTT (GRC)
numberNoJudgment number within the year
report_seriesNoLaw report series abbreviation: WLR, AC, QB, KB, Ch, All ER, EWCA Civ, etc.
volumeNoReport volume number (for law reports)
pageNoStarting page in the law report
legislation_titleNoTitle of legislation (for s.NN Act YYYY citations)
sectionNoSection number referenced
si_yearNoSI year (for SI YYYY/NNN citations)
si_numberNoSI number
resolved_urlNoTNA Find Case Law or legislation.gov.uk URL if successfully resolved
confidenceYesParse confidence 0.0–1.0. Citations below 0.7 are ambiguous and may have been sent for LLM disambiguation.
Behavior5/5

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

Discloses that raises ValueError on unrecognizable input, returns parsed fields and resolved_url, and is authoritative. No contradiction with annotations (readOnlyHint, idempotentHint). Adds value beyond annotations.

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?

Well-structured with bold imperative lead, but slightly verbose (e.g., 'Authoritative source' line). Every sentence adds value, and structure aids readability.

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?

With good annotations, 100% schema coverage, and an output schema present, the description covers the tool's behavior, error handling, and appropriate use cases. No gaps identified.

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 coverage is 100% with a clear description of the 'citation' parameter. The tool description does not add additional meaning beyond the schema's description.

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 it resolves a single OSCOLA citation to confirm it points to a real document, distinguishing it from parsing (sibling tool citations_parse). The verb 'resolve' and resource 'single OSCOLA citation' are specific.

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: 'BEFORE constructing an OSCOLA citation string from known fields' or to confirm a citation. Also provides when-not-to-use: if tool fails, do not manufacture citation. Includes context about fabrication risk.

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