UK Parliament MCP Server

get_answer_deadline

Calculate the answer deadline for a UK Parliament written question from its house, question type, and tabled date. Returns the earliest due date for Commons questions.

Instructions

Get answer deadline | PQ answer date, response deadline, when answers due | Get the earliest answer date for a written question (Commons only) | Returns answer deadline date

    Args:
        house: House: 'Commons' or 'Lords' (1 or 2 also accepted).
        question_type: Type of written question: 'NamedDay' or 'Ordinary'.
        tabled_date: Date the question was tabled (YYYY-MM-DD).

    Returns:
        Answer deadline date for the question.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`house`	Yes
`tabled_date`	Yes
`question_type`	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.9/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 burden. It does disclose a meaningful behavioral constraint ('Commons only') and the return value, but says nothing about error behavior when a non-Commons house is passed (despite the house param accepting 'Lords'), permission needs, or how deadlines are computed.

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 Args/Returns structure is readable and front-loads the purpose, but the opening pipe-separated keyword line ('PQ answer date, response deadline, when answers due') is search-bait that duplicates the purpose statement without adding meaning. Trimming it would tighten the definition.

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 low-complexity, 3-required-param tool with an output schema present, the definition covers purpose, all params, and the return value, so an agent can call it correctly. The only gap is the unresolved tension between 'Commons only' and a house parameter that accepts 'Lords'.

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

Parameters5/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 documents all three parameters, gives accepted values for house ('Commons'/'Lords', 1 or 2 also accepted), enumerates question_type values ('NamedDay'/'Ordinary'), and specifies the tabled_date format (YYYY-MM-DD). This is exactly the detail the schema omits.

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 the earliest answer date for a written question') and adds a scope constraint ('Commons only'). The keyword line ('PQ answer date, response deadline, when answers due') reinforces the resource domain, making it easy to separate from siblings like get_written_question or search_written_questions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: you use it when you have a house, question type, and tabled date and want the deadline. There is no explicit when-to-use vs when-not-to-use guidance or pointer to a related tool (e.g. get_written_question, get_tabling_deadline). The 'Commons only' note is a partial scoping hint.

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

Deploy Server