UK Parliament MCP Server

get_written_statement_by_uin

Retrieve a UK Parliament written statement by date and its UIN reference. Use when you have the official UIN to get full statement text, minister, and department details.

Instructions

Get a written statement by date and UIN (Unique Identification Number) | statement by reference, UIN lookup, official statement number | Use when you have a statement's official UIN reference number to retrieve the full statement details | Returns complete statement with minister, department, and full statement content

    Args:
        date: Date the statement was made in YYYY-MM-DD format.
        uin: The Unique Identification Number (UIN) of the statement.
        expand_member: Whether to include full member details. Default: True.

    Returns:
        Complete written statement details including statement text and minister information.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`uin`	Yes
`date`	Yes
`expand_member`	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

A4/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 does disclose the return shape (minister, department, full statement content) and the expand_member default, which is useful. However, it says nothing about permissions, error behavior when the UIN/date pair does not match, or pagination, leaving real gaps for a read tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence is front-loaded and clear, but the pipe-separated keyword list ('statement by reference, UIN lookup, official statement number') is filler, and the 'Returns' block duplicates information already carried by the output schema. The Args section is justified since the schema has no descriptions.

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, the description need not explain return values, and it correctly covers the two required params plus the optional one. Given 0% schema coverage and no annotations, the documentation of parameters is the important gap it fills; missing failure modes are a minor residual gap.

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%, so the description must compensate, and it largely does: it gives the date format (YYYY-MM-DD), explains UIN as the Unique Identification Number, and states expand_member's default of True. The only shortfall is that it does not explain what expand_member actually controls in the response beyond 'full member details'.

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 names a specific verb and resource ('Get a written statement') and pins it to a unique key ('by date and UIN'), which cleanly separates it from siblings get_written_statement and search_written_statements. An agent can tell what this retrieves without opening the schema.

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?

It states the selecting condition explicitly: 'Use when you have a statement's official UIN reference number.' That is clear context, but it never names the alternatives (get_written_statement, search_written_statements) even though they are close siblings, so the routing guidance is incomplete rather than exhaustive.

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

Deploy Server