UK Parliament MCP Server

get_erskine_may_index_term

Fetch details and paragraph references for an Erskine May index term after browsing the index, so you can explore UK Parliament procedure topics.

Instructions

Get details of an index term | procedure topic, references | Use after browsing index to get term details | Returns index term with all paragraph references.

    Args:
        index_term_id: Index term ID (from browse_erskine_may_index).

    Returns:
        Index term with paragraph references.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`index_term_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 6, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the return content ('index term with all paragraph references') and the required input origin, but never states this is a read-only operation or describes error/empty behavior. Adequate but with clear gaps for an unannotated 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?

The pipe-delimited lead sentence is front-loaded and scannable. The Args/Returns blocks are somewhat redundant with the structured schema, but overall the entry is short and free of filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be re-explained, and the description correctly covers purpose, workflow, and input origin. The only omission is the read-only/safety profile, which for an unannotated tool would have added value.

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 0% and the single parameter has no schema description, so the description must compensate. It does by identifying the parameter's source ('from browse_erskine_may_index'), which is genuinely useful provenance an agent needs to supply a valid ID.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Combines a specific verb and resource ('Get details of an index term') and clarifies the content ('procedure topic, references'), which distinguishes it from browsing/searching siblings. It stops short of naming a specific alternative sibling except implicitly through the workflow hint.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use after browsing index to get term details' establishes the workflow position and implies browse_erskine_may_index as the prerequisite step. Clear context is given, though no explicit when-not or alternative-exclusion is stated.

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

Deploy Server