UK Parliament MCP Server

get_member_written_questions

Retrieve written questions a UK Parliament member has submitted by member ID. Use it to research their parliamentary inquiries and questions to government departments.

Instructions

Get written questions submitted by a member by ID. Use when researching what questions a member has asked of government departments or their areas of parliamentary inquiry. See also: search_written_questions.

    Args:
        member_id: Parliament member ID to get written questions for.
        page: Optional: page number for pagination.

    Returns:
        Written questions submitted by the member.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`member_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.6/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 that this is a filtered read returning a member's written questions and hints at pagination via the page arg, but omits any auth requirements, result limits, or pagination behavior beyond the schema.

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?

Front-loads purpose in the first sentence and organizes supplementary detail into Args/Returns sections. No filler, though the Returns line is somewhat redundant given an output schema exists.

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 return values need no elaboration, and the description nonetheless covers purpose, usage context, and both parameters. The main gap for a zero-annotation tool is the lack of any behavioral/operational detail such as pagination semantics or ordering.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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. It does describe both parameters ('member_id: Parliament member ID' and 'page: Optional: page number for pagination'), supplying minimal but real meaning over the bare schema titles, though nothing about format or bounds.

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+resource ('Get written questions submitted by a member by ID'), which clearly identifies both the operation and the entity. It names the sibling 'search_written_questions' as related, aiding differentiation, though it does not spell out the exact contrast between them.

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?

Provides clear context for use ('when researching what questions a member has asked of government departments or their areas of parliamentary inquiry') and points to 'search_written_questions' as a related tool. It stops short of stating explicit when-not conditions or which of the two tools to choose.

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

Deploy Server