Skip to main content
Glama
paulieb89

UK Legal Research MCP Server

Get Legislation Section

legislation_get_section
Read-onlyIdempotent

Retrieve specific sections from UK Acts and Statutory Instruments to access full text, territorial extent, and in-force status for legal research and compliance verification.

Instructions

Retrieve a specific section of a UK Act or Statutory Instrument.

Returns the full section text, territorial extent, in-force status, and prospective flag. Content is capped per max_chars (default 10,000, ~2,500 tokens) — raise max_chars for unusually long definition sections. Check content_truncated in the response to see if it was cut.

IMPORTANT: Always check extent — a section may apply to England & Wales but not Scotland or Northern Ireland.

Alternative: read the resource template legislation://{type}/{year}/{number}/section/{section} to get raw CLML XML directly. Use this tool when you want the parsed structured response (extent, in-force, version_date) instead of raw XML.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYestype, year, number, section identifier, optional max_chars.

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'
version_dateNoDate of the version retrieved
prospectiveNoTrue if this section has not yet come into force
Behavior4/5

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

The description adds valuable behavioral context beyond annotations: content truncation behavior with max_chars parameter, the need to check content_truncated in response, and the territorial extent consideration. While annotations cover safety (readOnlyHint=true, destructiveHint=false), the description provides practical implementation details that help the agent use the tool correctly.

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 efficiently structured with clear sections: purpose statement, return values, important usage note, and alternative guidance. Every sentence adds value - no redundant information. It's front-loaded with the core purpose and progressively adds important details.

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 tool has comprehensive annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint), 100% schema coverage, and an output schema exists, the description provides complete contextual information. It covers purpose, usage guidance, behavioral nuances, and alternatives without needing to explain return values or safety aspects already covered elsewhere.

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?

With 100% schema description coverage, the schema already documents all parameters thoroughly. The description adds some context about max_chars (default covers most sections, raise for long Finance Act definitions) and mentions schedules aren't supported, but doesn't provide significant additional parameter semantics beyond what's in 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 clearly states the verb 'retrieve' and resource 'specific section of a UK Act or Statutory Instrument', distinguishing it from sibling tools like legislation_search (which searches) and legislation_get_toc (which gets table of contents). It specifies the exact type of legislation content being accessed.

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 provides explicit guidance on when to use this tool versus the alternative (raw XML access via read_resource template), stating 'Use this tool when you want the parsed structured response instead of raw XML.' It also includes an important usage note about checking territorial extent.

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