Skip to main content
Glama
paulieb89

UK Legal Research MCP Server

Get Legislation Section

legislation_get_section
Read-onlyIdempotent

Retrieve a specific section of a UK Act or Statutory Instrument, returning its full text, territorial extent, in-force status, and prospective flag.

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
Behavior5/5

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

Discloses behavioral traits beyond annotations: content truncation at max_chars, default and recommended max_chars values, and the need to check `content_truncated` in the response. Annotations already declare readOnlyHint, destructiveHint false, idempotentHint true, and the description adds valuable context without contradiction.

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?

Every sentence adds value: purpose, return fields, truncation behavior, territorial extent note, and alternative tool. No redundancy, front-loaded with key action. Efficiently structured in three short paragraphs with clear signals (e.g., 'IMPORTANT').

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, the description does not need to detail return structure extensively. It covers all needed context: what is returned (full text, extent, in-force status, prospective flag), truncation behavior, territorial extent caveat, and alternative. Completes the picture for a retrieval tool with no missing gaps.

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 coverage is 100%, so baseline is 3. The description adds meaningful guidance: explains `section` should be numeric only and schedules unsupported, and provides practical advice for `max_chars` (default 10k, raise for long definitions, check truncation flag). This goes beyond schema descriptions, warranting a 4.

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 'Retrieve a specific section of a UK Act or Statutory Instrument', which clearly identifies the verb and resource. It distinguishes from sibling tools like legislation_get_toc and legislation_search by specifying the structured response format (extent, in-force status) versus raw XML, making it easy to select correctly.

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?

Provides explicit guidance on when to use this tool ('parsed structured response') versus the alternative resource template for raw CLML XML. Includes critical usage notes: always check `extent` for territorial application, and adjust max_chars for long sections. No exclusion criteria, but the alternative is clearly stated.

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