UK Parliament MCP Server

get_events

Search UK Parliament committee events by date, house, type, location, or committee to find meetings, hearings, and other activities.

Instructions

Search for committee events with flexible filtering options. Use when you need to find meetings, hearings, or other committee activities by date, location, or committee. Supports filtering by start/end dates, house, event type, and location.

    Args:
        committee_id: Optional: filter by specific committee ID.
        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:
        Committee events matching the criteria.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`skip`	No
`take`	No
`location_id`	No
`search_term`	No
`committee_id`	No
`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.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 full behavioral burden. It is implicitly a read/search operation and it usefully discloses pagination constraints ('default 30, max 100'), which is real behavioral context. It still omits permission requirements, rate limits, and what 'include_event_attendees' changes in payload size/cost.

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?

Purpose is front-loaded and the Args list is structured, but the opening sentence already lists the filterable fields that the Args section then repeats, and it references a 'house' filter that does not correspond to any parameter in the schema. That duplication and slight inaccuracy cost efficiency.

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 tool with no annotations and 0% schema coverage, the description is thorough: every parameter is described and the return is summarized, with an output schema covering payload shape. Missing only default sort direction and any note on how the many date/type filters combine.

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 largely does: it documents all 14 parameters, supplies date formats (YYYY-MM-DD), and gives pagination defaults and a max. A few entries are near-tautological ('committee_business_id: filter by committee business ID'), keeping it short of 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 ('Search for committee events') and enumerates the filterable dimensions (dates, location, committee, event type). It is clear on its own, but it does not distinguish itself from close siblings such as get_committee_events, search_event_activities, or get_committees_next_events, so an agent cannot tell from the description alone which event tool to pick.

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 need to find meetings, hearings, or other committee activities by date, location, or committee' gives implied usage context. However, it offers no when-not guidance, no prerequisites, and never names an alternative among the many event-related siblings, leaving routing to inference.

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

Deploy Server