UK Parliament MCP Server

get_publication_by_id

Retrieve detailed information about a specific UK Parliament committee publication by ID, including documents, HC numbers, government responses, and committee business.

Instructions

Get detailed information about a specific committee publication by ID. Use when you need complete publication details including documents, HC numbers, government responses, and associated committee business.

    Args:
        publication_id: Unique publication ID number.
        show_on_website_only: Show only publications visible on website.

    Returns:
        Detailed information about the publication.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`publication_id`	Yes
`show_on_website_only`	No

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 full behavioral burden. It implies a read-only fetch and enumerates the kinds of content returned, but says nothing about invalid-ID behavior, error responses, or whether the ID namespace is committee-specific vs global.

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 core purpose is front-loaded in the first sentence, followed by usage. The Args/Returns blocks are somewhat redundant with the schema and output schema, but the overall text is short and readable.

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?

For a two-parameter read tool with an output schema already covering return shape, the description supplies the purpose, usage context, and both parameter meanings. Only error/edge-case behavior for an invalid ID is left unaddressed.

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 0%, yet the description compensates by defining both parameters: publication_id as a 'Unique publication ID number' and show_on_website_only as filtering to website-visible publications. It omits the default value (true), which the schema itself supplies.

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?

States a specific verb and resource ('Get detailed information about a specific committee publication by ID'), which is clearer than the sibling get_publications and distinct from get_publication_document. It does not explicitly contrast itself against nearby siblings like get_committee_publications_summary, so it stops short of a 5.

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 when you need complete publication details including documents, HC numbers, government responses, and associated committee business' gives a clear trigger condition. There are no explicit exclusions or named alternatives, which is the only gap.

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

Deploy Server