UK Parliament MCP Server

get_committee_meetings

Search UK Parliament committee meetings and hearings by date range to check schedules, plan attendance, or research past activity. Returns committees, dates, times, and topics.

Instructions

Find committee meetings and hearings by date range | committee meetings, parliamentary hearings, committee schedule, committee calendar, when committees meet | Use for finding committee schedules, planning attendance, or researching past committee activity | Returns meeting details including committees, dates, times, and topics | Covers both Commons and Lords committees See also: get_events, get_committees_next_events.

    Args:
        from_date: Start date. Format: YYYY-MM-DD. Example: 2024-01-15
        to_date: End date. Format: YYYY-MM-DD. Must be after start date.

    Returns:
        Meeting details including committees, dates, times, and topics.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to_date`	Yes
`from_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

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 scope (Commons and Lords) and return content, and adds a validation rule ('to_date must be after start date'), but says nothing about pagination, result limits, sorting, or read-only nature. Useful context, but not the rich disclosure an un-annotated query tool warrants.

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 is front-loaded, but the pipe-separated keyword block ('committee meetings, parliamentary hearings, committee schedule, committee calendar, when committees meet') is SEO filler, and the return sentence is duplicated verbatim in the Args/Returns section. Some trimming would sharpen it.

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 needn't be spelled out. The description covers purpose, scope, parameters, and validation, which is close to complete for a two-param date-range query; only pagination/limit behavior is missing.

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% (properties carry only titles), so the description must compensate, and it does: it specifies the YYYY-MM-DD format with a worked example for from_date and the ordering constraint for to_date. This meaningfully exceeds the bare schema.

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 ('Find committee meetings and hearings by date range') and explicitly scopes coverage to both Commons and Lords committees. The 'See also' pointer to get_events and get_committees_next_events lets an agent separate it from closely-named siblings without opening a 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?

Gives concrete use cases ('finding committee schedules, planning attendance, or researching past committee activity') and names two alternative tools. However, it never states when NOT to use this tool or the routing condition that selects get_committee_events vs get_events, so the alternatives are listed rather than explained.

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

Deploy Server