UK Parliament MCP Server

get_written_question

Fetch full details of a UK Parliament written question using its ID, including question text, answer, and member information.

Instructions

Get a specific written question by ID | written question details, PQ lookup, question by ID | Use when you have a question ID and need full details including the question text, answer, and member information | Returns complete question with asking member, answering body, question text, and answer

    Args:
        question_id: The unique ID of the written 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
`question_id`	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 discloses the return contents (asking member, answering body, question text, answer) and the expand_member default, but says nothing about permissions, read-only nature, or any side effects. Adequate but not rich.

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?

Front-loads the core purpose, but the pipe-delimited keyword line ('written question details, PQ lookup, question by ID') is largely redundant padding, and the Args/Returns sections restate what the schema and output schema already convey.

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, the description covers purpose, trigger condition, both parameters, and the return shape. Nothing critical for correct invocation is missing, though permission/behavioral context is thin.

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 does: it explains question_id as the unique ID and expand_member as controlling inclusion of full member details with a stated default of True. That is meaningful beyond the bare schema types.

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 ('Get a specific written question by ID') and its scope, clearly separating it from siblings like search_written_questions and get_written_question_by_uin. An agent can identify the retrieval-by-ID intent 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?

'Use when you have a question ID and need full details including the question text, answer, and member information' gives a clear triggering condition. It does not name when to prefer get_written_question_by_uin or search_written_questions instead, so it stops short of explicit alternatives.

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

Deploy Server