UK Parliament MCP Server

get_written_question_by_uin

Retrieve a UK Parliament written question by its official UIN and tabling date. Returns full question text, answer, asking member, and answering body.

Instructions

Get a written question by date and UIN (Unique Identification Number) | question by reference, UIN lookup, official question number | Use when you have a question's official UIN reference number to retrieve the full question details | Returns complete question with asking member, answering body, question text, and answer

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

    Returns:
        Complete written question details including question text, answer, and member 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

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the return contents (question text, answer, member info) and the expand_member toggle, but says nothing about permissions, rate limits, or whether the record can be missing. Adequate but thin for an annotation-free tool.

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 purpose and usage are front-loaded, which is good, but the leading clause stacks near-synonyms ('question by reference, UIN lookup, official question number') that read as keyword stuffing, and the Returns section partly duplicates the opening sentence.

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?

An output schema exists, so the description needn't detail the response format, and all three parameters are documented. For a simple read-by-identifier tool the definition covers what an agent needs, with only minor behavioral 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 0%, so the description must compensate, and it does: it defines date as the tabling date in YYYY-MM-DD format, explains UIN, and notes expand_member defaults to True. It leaves the meaning of 'full member details' when expand_member is false somewhat unclear.

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?

The description names a specific verb and resource ('Get a written question by date and UIN') and gives the distinguishing retrieval key (official UIN reference). It implicitly separates itself from search-based siblings, though it never explicitly names get_written_question or search_written_questions as alternatives.

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 explicitly states the triggering condition: 'Use when you have a question's official UIN reference number to retrieve the full question details.' This tells the agent the precondition, but it does not name the sibling to use when the UIN is not known (e.g. search_written_questions).

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

Deploy Server