MCP server for UK legislation (legislation.gov.uk), case law (Find Case Law) and GOV.UK tribunal decisions, HMRC manuals and CMA cases — with persistent identifiers and verifiable citations.
Strong tool naming (all verb_noun pattern: gb_get_*, gb_search_*) and comprehensive descriptions (avg 180 chars, well above 10-char minimum). All 9 tools have input schemas with types and descriptions. Output schemas are documented in descriptions but not formally in JSON Schema. Error handling guidance is present in INSTRUCTIONS but not per-tool. Security is solid (read-only operations, no secrets in params). Main gaps: output schemas not formally declared in tool definitions; no pagination metadata (total_count, next_cursor) in search results; some parameter descriptions could be more prescriptive about format/constraints.
Declare what this connector covers, how it is sourced, and what it does not cover. Returns families of data (Legislation, Case law, Government guidance), sources, and known gaps with fallback instructions.
Fetch metadata for a UK act or instrument by reference (e.g. ukpga/2018/12 for the Data Protection Act 2018, or a full legislation.gov.uk URL). Returns metadata including title, description, enactment date, and citation information.
Fetch a judgment by neutral citation (e.g. '[2026] EWHC 1698 (Admin)') or a Find Case Law URI/path. Returns Akoma Ntoso XML content when derivable, else the PDF link.
Fetch one GOV.UK document by its link path via the Content API (/api/content/{path}). Tribunal decisions return metadata + the judgment PDF in attachments; HMRC manual sections return the full text in body_html.
Fetch the full text of a UK act or instrument in a specified format (xml, html, akn, rdf, pdf, or csv). Returns the manifestation for the given reference and format.
Output schemas not formally declared in tool definitions. Descriptions mention return types (e.g., 'Returns metadata including title, description, enactment date') but JSON Schema output is absent. LLMs cannot reliably parse unstructured responses.
Search tools (gb_search, gb_search_case_law, gb_search_govuk) lack pagination metadata. Descriptions mention 'paginate with page/limit' but do not specify whether results include total_count, next_cursor, or has_more. LLMs cannot determine if more results exist without explicit metadata.
Parameter descriptions lack prescriptive format constraints. E.g., 'reference' param accepts 'ukpga/2018/12' or 'full legislation.gov.uk URL' but no regex pattern or format hint. 'ISO 8601 date' is mentioned but not validated with a pattern constraint. LLMs may pass invalid formats.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 65 | 2026-07-28+ | v2 |
Fetch legislation published since a given ISO 8601 date, newest-first, optionally filtered by document type. Useful for a law-monitoring feature.
Full-text/title search of UK legislation via the official Atom search feed. Filter by document type (e.g. ukpga, uksi, asp, nia, wsi) and/or year; paginate with page parameter.
Full-text search of UK judgments via the public Find Case Law Atom feed (caselaw.nationalarchives.gov.uk/atom.xml). Filter by court (e.g. ewhc/admin, ewca/civ, uksc), from_date/to_date (applied client-side), paginate with limit.
Full-text search of GOV.UK via its Search API (/api/search.json, keyless). Filter by document_type (employment_tribunal_decision, hmrc_manual_section, residential_property_tribunal_decision, employment_appeal_tribunal_decision, cma_case, utaac_decision, tax_tribunal_decision, asylum_support_decision, organisation), from_date/to_date (server-side), limit, start.
Error handling guidance exists in INSTRUCTIONS but not per-tool. No tool-level error responses documented (e.g., 'If reference not found, try gb_search()'). Agents lack recovery paths at the tool level.
gb_coverage tool has no input parameters but description is vague ('Declare what this connector covers'). Purpose is clear from context but description could be more actionable: 'Returns data families (Legislation, Case law, Government guidance), sources, and known gaps to guide tool selection.'