UK Parliament MCP Server

get_tabling_deadline

Find the UK Parliament tabling deadline for a chosen house and date, so you can submit questions or EDMs on time.

Instructions

Get tabling deadline | table questions, submission deadline, EDM deadline | Get the valid tabling date for a specified date (Commons only) | Returns tabling deadline date

    Args:
        house: House: 'Commons' or 'Lords' (1 or 2 also accepted).
        requested_date: Date to find tabling deadline for (YYYY-MM-DD).

    Returns:
        Tabling deadline date for the specified house.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`house`	Yes
`requested_date`	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

B3/5.0

Behavior2/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 says nothing about permissions, whether the deadline is a fixed or computed value, or how non-sitting days are handled. The '(Commons only)' constraint is the one behavioral claim, and it conflicts with the house parameter that accepts Lords, muddying rather than clarifying behavior.

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 pipe-delimited header repeats the tool name and lists loosely related concepts ('table questions, submission deadline, EDM deadline') that aren't otherwise explained, and the 'Returns' line restates the purpose line. The Args section is useful, but the definition is padded rather than front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 not be explained, and both required params are covered. However, the internal Commons-vs-Lords contradiction is unresolved and there is no routing guidance among the many deadline/calendar siblings, leaving an agent to guess in edge cases.

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: house is documented as 'Commons' or 'Lords' with 1/2 also accepted, and requested_date is documented as YYYY-MM-DD. This adds real meaning beyond the bare anyOf/string schema, though it doesn't explain what happens for invalid values.

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 ('Get') and resource ('tabling deadline') and clarifies it returns the valid tabling date for a given date. It is distinguishable from calendar/deadline siblings by naming tabling specifically, but it never explicitly contrasts with near neighbors like get_answer_deadline or get_submission_period.

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

Usage Guidelines2/5

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

No statement of when to use this versus alternatives; the only scoping hint is a parenthetical '(Commons only)', which is immediately undercut by the house argument accepting 'Commons' or 'Lords'. No prerequisites or when-not-to-use guidance is given.

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

Deploy Server