UK Business Tools - Ledgerhall

Get Legislation Table of Contents

law_legislation_get_toc

Read-onlyIdempotent

USE THIS TOOL WHEN you have a known Act / SI and want the structural table of contents (parts, chapters, individual sections/regulations/articles).

Returns XML ids and titles in document order, including Parts, chapters, crossheadings, and provisions; a rare untitled provision is retained as its bare id. Results are paginated with offset/limit.

AFTER calling, pass a provision's bare number (for example 47, not section-47) to legislation_get_section. Check has_more and total_items for large statutes. Use read_resource with the legislation:// toc URI for the full raw listing.

Source: legislation.gov.uk CLML table of contents.

Input Schema

Name	Required	Description
`type`	Yes	Legislation type code: 'ukpga' (Acts), 'uksi' (SIs), 'asp' (Scottish Acts), 'nia' (NI Acts). Use the value from legislation_search results.
`year`	Yes	Year of enactment
`limit`	No	Maximum items to return in this call (default 200, max 1000). Raise only when you need a larger slice in one response. Check has_more and total_items to know if further pages exist.
`number`	Yes	Chapter or SI number
`offset`	No	Number of items to skip from the flattened TOC. Use with limit to page through very large statutes like the Companies Act 2006 (1300+ items).

Output Schema

Name	Required	Description
`type`	Yes	Legislation type code echoed from the request
`year`	Yes	Year of enactment echoed from the request
`items`	No	TOC entries in XML document order, formatted as '<id>: <title>', e.g. 'section-47: Definitions'. When calling legislation_get_section pass only the numeric part ('47', not 'section-47').
`limit`	Yes	Page size applied after offset
`number`	Yes	Chapter or SI number echoed from the request
`offset`	Yes	Offset applied to the full TOC item list
`has_more`	Yes	True if more items remain beyond offset+returned
`returned`	Yes	Number of items in this response
`total_items`	Yes	Total structural items parsed from the XML, before offset/limit. Compare to `returned` and `has_more` to decide whether to paginate.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedJun 14, 2026

addedInput schema / properties / limit

Added value: +{
+  "default": 200,
+  "description": "Maximum items to return in this call (default 200, max 1000). Raise only when you need a larger slice in one response. Check has_more and total_items to know if further pages exist.",
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / number

Added value: +{
+  "description": "Chapter or SI number",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Number of items to skip from the flattened TOC. Use with limit to page through very large statutes like the Companies Act 2006 (1300+ items).",
+  "minimum": 0,
+  "type": "integer"
+}

removedInput schema / properties / params

Removed value: -{
-  "additionalProperties": false,
-  "description": "LegislationGetTocInput.",
-  "properties": {
-    "limit": {
-      "default": 200,
-      "description": "Maximum items to return in this call (default 200, max 1000). Raise only when you need a larger slice in one response. Check has_more and total_items to know if further pages exist.",
-      "maximum": 1000,
-      "minimum": 1,
-      "type": "integer"
-    },
-    "number": {
-      "description": "Chapter or SI number",
-      "minimum": 1,
-      "type": "integer"
-    },
-    "offset": {
-      "default": 0,
-      "description": "Number of items to skip from the flattened TOC. Use with limit to page through very large statutes like the Companies Act 2006 (1300+ items).",
-      "minimum": 0,
-      "type": "integer"
-    },
-    "type": {
-      "description": "Legislation type code: 'ukpga' (Acts), 'uksi' (SIs), 'asp' (Scottish Acts), 'nia' (NI Acts). Use the value from legislation_search results.",
-      "maxLength": 10,
-      "minLength": 2,
-      "type": "string"
-    },
-    "year": {
-      "description": "Year of enactment",
-      "maximum": 2100,
-      "minimum": 1800,
-      "type": "integer"
-    }
-  },
-  "required": [
-    "type",
-    "year",
-    "number"
-  ],
-  "type": "object"
-}

addedInput schema / properties / type

Added value: +{
+  "description": "Legislation type code: 'ukpga' (Acts), 'uksi' (SIs), 'asp' (Scottish Acts), 'nia' (NI Acts). Use the value from legislation_search results.",
+  "maxLength": 10,
+  "minLength": 2,
+  "type": "string"
+}

addedInput schema / properties / year

Added value: +{
+  "description": "Year of enactment",
+  "maximum": 2100,
+  "minimum": 1800,
+  "type": "integer"
+}

changedInput schema / required

Previous value: -[
-  "params"
-]New value: +[
+  "type",
+  "year",
+  "number"
+]

Changed1 schema field changedMay 30, 2026

changedInput schema / properties / params / description

Previous value: -"LegislationGetTocInput with type, year, number, offset, limit."New value: +"LegislationGetTocInput."

Changed1 schema field changedMay 29, 2026

changedOutput schema / properties / total_items / description

Previous value: -"Total number of structural items parsed from the XML, before offset/limit. Use this to know the full size of the TOC."New value: +"Total structural items parsed from the XML, before offset/limit. Compare to `returned` and `has_more` to decide whether to paginate."

AddedMay 16, 2026
RemovedMay 16, 2026
First observedMay 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the description is not burdened with safety disclosure. It still adds real context: document-order return, inclusion of crossheadings and provisions, retention of untitled provisions as bare ids, pagination via offset/limit, and the CLML data source. Missing only permission/rate-limit notes, which are likely irrelevant for a public read tool.

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?

Front-loaded with the trigger condition, followed by return shape, pagination, and next-step instructions — all useful. The trailing 'Source: legislation.gov.uk CLML' line is minor provenance noise, and the pagination note partially duplicates the schema defaults.

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 an output schema present, the description need not explain return values, yet it still tells the agent which response fields to watch (has_more, total_items) for large statutes and what to do on the next call. Nothing needed to call this tool correctly is absent.

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 the baseline is 3. The description goes a step beyond by telling the agent to take the type value from legislation_search results and to reuse bare provision numbers consistently, linking the required tuple semantics to the surrounding workflow.

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?

States a specific verb and resource ('structural table of contents' of a known Act/SI) and enumerates the structural elements returned (parts, chapters, sections/regulations/articles). This clearly distinguishes it from law_legislation_search (which finds the Act) and law_legislation_get_section (which fetches provision text).

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?

Opens with an explicit trigger ('USE THIS TOOL WHEN you have a known Act / SI'), names the downstream tool for the next step (legislation_get_section), and names an alternative path (read_resource with the legislation:// toc URI for the full raw listing). The condition implicitly excludes searching, complementing the sibling search tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All UK Business Tools - Ledgerhall tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?