Skip to main content
Glama
paulieb89

UK Legal Research MCP Server

Get Legislation Section

legislation_get_section
Read-onlyIdempotent

Get the parsed text of a specific UK legislation section, along with territorial extent and in-force status. Essential for verifying which jurisdictions a section applies to.

Instructions

USE THIS TOOL WHEN you have a known Act / SI and want the parsed text of a specific section, with extent and in-force metadata.

Returns full section text, territorial extent, in-force status, and prospective flag. Content capped per max_chars (default 10,000, ~2,500 tokens) — raise for unusually long definition sections; check content_truncated in the response.

ALWAYS check extent — a section may apply to England & Wales but not Scotland or Northern Ireland. Reciting a section without checking extent is a recurring legal-research error.

Alternative: call read_resource(uri="legislation://{type}/{year}/{number}/ section/{section}") for raw CLML XML; use this tool when you want the parsed structured response instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYesLegislationGetSectionInput.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesSection title or heading
section_numberYesSection number, e.g. '47', '12A', 'Schedule 2'
contentYesPlain text content of the section, possibly truncated per max_chars. Check content_truncated and original_length for full-text information.
content_truncatedNoTrue if content was cut to fit max_chars
original_lengthNoOriginal plain-text length in characters before any truncation
in_forceNoWhether this section is currently in force; None if unknown
extentNoTerritorial extent: list of 'England', 'Wales', 'Scotland', 'Northern Ireland'. Empty list means unknown — do not assume full UK extent.
version_dateNoDate of the version retrieved
prospectiveNoTrue if this section has not yet come into force; None if unknown
source_formatNoSource parsed for this response. html_fallback means CLML XML was unavailable and text was parsed from the public HTML page.xml
warningsNoNon-fatal retrieval or parsing warnings the caller should disclose where relevant.
Behavior4/5

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

Annotations already indicate `readOnlyHint: true` and `idempotentHint: true`. The description adds value by explaining content truncation via `max_chars` (with default and recommendations), the `content_truncated` response field, and the presence of `extent` and `in-force` metadata. No contradictions with 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?

The description is well-structured: a purpose-first sentence, then explicit usage guidelines, followed by details on behavior and alternatives. It is front-loaded and each sentence serves a purpose. Slight verbosity in the max_chars comment but overall efficient.

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 presence of an output schema (from context signals), the description does not need to explain return values. It already covers purpose, use-cases, parameter nuances, behavioral limits, error prevention (extent check), and an alternative. This is comprehensive for a complex legal tool.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds extra meaning for `type` (use from search results), `section` (numeric only, no schedules), and `max_chars` (default, maximum, and tip for long sections). These elaborations improve usability beyond the 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 explicitly states the verb ('Get Legislation Section'), the resource ('a specific section' from a known Act/SI), and the scope ('parsed text...with extent and in-force metadata'). It also distinguishes from the sibling `read_resource` tool for raw XML, making purpose unambiguous.

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 begins with 'USE THIS TOOL WHEN you have a known Act / SI', providing clear context. It explicitly names an alternative (`read_resource`) and explains when to use each. It also includes a critical warning about checking `extent` to avoid common legal-research errors.

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