UK Parliament MCP Server

get_parliamentary_diary

Retrieve upcoming UK Parliament business and events for Commons or Lords by date or keyword. Filter the parliamentary diary to plan coverage or track schedules.

Instructions

Get parliamentary diary | diary, schedule, events, business programme | Retrieve the parliamentary diary with upcoming business and events | Returns diary events

    Args:
        house: Optional house filter: 'Commons' or 'Lords' (1 or 2 also accepted).
        start_date: Optional start date filter (YYYY-MM-DD). Defaults to today when no date filter is given.
        end_date: Optional end date filter (YYYY-MM-DD).
        date: Optional specific date filter (YYYY-MM-DD).
        category_id: Optional category ID to filter by.
        search_term: Optional search term to filter events.

    Returns:
        Parliamentary diary events matching the filter criteria.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No
`house`	No
`end_date`	No
`start_date`	No
`category_id`	No
`search_term`	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.5/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 burden. It usefully discloses defaulting behavior (today) and accepted input formats, which is real behavioral context. However it says nothing about result volume, pagination, sort order, or timezone — gaps for a diary feed that may return many events.

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 sentence is front-loaded and the Args block is tight, but the leading pipe-delimited keyword line ('diary, schedule, events, business programme') merely restates the name and the return sentence ('Returns diary events') duplicates the Returns section — two passages that do not earn their place.

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?

With 6 parameters, 0% schema coverage, and an output schema present, the description does what it needs to: it documents every input and defers return-value detail to the output schema. Only the undiscoverable category_id values and pagination behavior keep it from a 5.

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 largely does: all six params are documented with formats (YYYY-MM-DD), accepted values ('Commons'/'Lords', 1 or 2), and optionality. The one gap is category_id, whose valid values are never hinted at (e.g. via get_calendar_categories).

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 and resource: 'Retrieve the parliamentary diary with upcoming business and events.' An agent can tell this apart from calendar-adjacent siblings like search_calendar or get_sittings by the 'diary' resource. It does not explicitly name a sibling it differs from, so it stops short of a 5.

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?

Gives one concrete usage rule — 'Defaults to today when no date filter is given' — which tells the agent the no-arg call is valid and meaningful. Beyond that there is no when-to-use/when-not guidance and no routing to alternatives such as get_calendar_event or search_calendar.

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

Deploy Server