UK Parliament MCP Server

get_speaker_events

Retrieve UK Parliament speaker events filtered by house, date, category, or search term to view speakers, order paper, and business items.

Instructions

Get speaker events | speakers, order paper, business items, speakers list | Retrieve parliamentary events with speaker information | Returns speaker event details

    Args:
        house: Optional house filter: 'Commons' or 'Lords' (1 or 2 also accepted).
        start_date: Optional start date filter (YYYY-MM-DD).
        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 events with speaker information 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

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 implies a read-only lookup, but says nothing about pagination, result limits, authentication, or how filtering interacts (e.g. whether date and start_date/end_date can be combined). The 'Returns' line restates the purpose rather than disclosing 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 Args/Returns block is front-loaded and useful, but the opening pipe-delimited header says the same thing three times ('Get speaker events', 'Retrieve parliamentary events with speaker information', 'Returns speaker event details'), which is redundant filler rather than added information.

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-value explanation is not needed. The parameter documentation is adequate, but the description leaves the core concept ('speaker events' — order paper, business items) undefined and gives no basis for choosing this tool over the numerous sibling speaker/event tools, which is the main gap for a 6-param retrieval tool.

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: it documents all six parameters with accepted values and formats ('Commons' or 'Lords' or 1/2; YYYY-MM-DD dates) and labels each as optional. It doesn't explain category_id sourcing or search_term matching behavior, which keeps it below 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?

The description states a specific verb+resource: retrieve parliamentary events with speaker information, and the keyword list (speakers, order paper, business items, speakers list) hints at the domain. However, it does not distinguish this tool from close siblings like get_debate_speakers, get_hansard_speakers_for_day, or get_speaker_and_deputies, so an agent could easily pick the wrong one.

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?

There is no when-to-use guidance, no conditions selecting this over alternatives, and no exclusions. The Args list implies filter-based retrieval but never says in what scenario an agent should reach for this tool rather than the many other speaker/event tools.

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

Deploy Server