UK Parliament MCP Server

get_committee_events

Retrieve meetings and activities for a specific UK Parliament committee by ID. Filter by date range, business, event type, or location to find relevant committee events.

Instructions

Get events for a specific committee by committee ID. Use when you want to see all meetings and activities for a particular committee, with options to filter by date range, business, and event type.

    Args:
        committee_id: Committee ID to get events for.
        committee_business_id: Optional: filter by committee business ID.
        search_term: Optional: search term for event titles or content.
        start_date_from: Optional: start date from in YYYY-MM-DD format.
        start_date_to: Optional: start date to in YYYY-MM-DD format.
        end_date_from: Optional: end date from in YYYY-MM-DD format.
        location_id: Optional: location ID to filter events.
        exclude_cancelled_events: Optional: exclude cancelled events.
        sort_ascending: Optional: sort ascending by date.
        event_type_id: Optional: filter by event type ID.
        include_event_attendees: Include event attendees in response.
        show_on_website_only: Show only events visible on website.
        skip: Number of records to skip (for pagination).
        take: Number of records to return (default 30, max 100).

    Returns:
        Events for the specified committee.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`skip`	No
`take`	No
`location_id`	No
`search_term`	No
`committee_id`	Yes
`end_date_from`	No
`event_type_id`	No
`start_date_to`	No
`sort_ascending`	No
`start_date_from`	No
`show_on_website_only`	No
`committee_business_id`	No
`include_event_attendees`	No
`exclude_cancelled_events`	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.7/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 usefully discloses pagination controls (skip, take default 30, max 100) and implies a read-only operation via 'Get', but says nothing about permissions, error behavior on an invalid committee_id, or how the start_date vs end_date filters differ semantically.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and usage cue are front-loaded in the first sentence, and the Args block is long only because 14 parameters must be documented from zero schema coverage, so each line earns its place. The 'Returns' line is slightly redundant given an output schema exists but is one sentence.

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 14-parameter, no-annotation tool with an output schema, the definition covers purpose, filtering options, pagination and defaults, which is enough to call it correctly. It lacks any disambiguation from the heavily overlapping committee-event siblings, which is the remaining gap.

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 is the only source of parameter meaning, and it documents all 14 arguments including the YYYY-MM-DD date format and the max-100 pagination cap, which the schema omits. Some entries are thin or restate the name ('Optional: filter by committee business ID'), keeping it from a 5.

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 ('Get events') scoped to 'a specific committee by committee ID', which distinguishes it from the broad get_events sibling. It does not name any alternative sibling (get_events, get_committee_meetings, get_committees_next_events) that an agent must choose between, 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?

The sentence 'Use when you want to see all meetings and activities for a particular committee' gives a clear usage context, but there is no when-not guidance and no routing against the many overlapping committee/event siblings. The agent is left to infer that this is the per-committee variant of get_events.

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

Deploy Server