UK Parliament MCP Server

search_early_day_motions

Search UK Parliament Early Day Motions by topic, member, date, or status to find backbench motions, MP opinions, and prayers against statutory instruments, with sponsors and signature counts.

Instructions

Search EDMs by topic | Early Day Motions, backbench motions, MP opinions, prayers against SIs | Use to find motions on specific issues, by member, or withdrawn motions | Returns EDMs with sponsors and signature counts See also: get_early_day_motion, edms_for_member_id, get_recently_tabled_edms.

    Args:
        search_term: Optional: search term for EDM topics or content.
        member_id: Optional: filter by member ID (tabled or sponsored by).
        include_sponsored_by_member: Optional: include EDMs where member is a sponsor (not just primary).
        statuses: Optional: filter by status - 'Published' or 'Withdrawn'.
        tabled_start_date: Optional: EDMs tabled on or after this date (YYYY-MM-DD).
        tabled_end_date: Optional: EDMs tabled on or before this date (YYYY-MM-DD).
        is_prayer: Optional: filter to prayers against negative Statutory Instruments.
        order_by: Optional: 'DateTabledAsc', 'DateTabledDesc', 'TitleAsc', 'TitleDesc', 'SignatureCountAsc', 'SignatureCountDesc'.
        skip: Number of records to skip (for pagination).
        take: Number of records to return (default 25, max 100).

    Returns:
        EDMs matching the search criteria with sponsors and signature counts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`skip`	No
`take`	No
`order_by`	No
`statuses`	No
`is_prayer`	No
`member_id`	No
`search_term`	No
`tabled_end_date`	No
`tabled_start_date`	No
`include_sponsored_by_member`	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

A4.2/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 pagination defaults ('take' default 25, max 100), filterable statuses, and return contents (sponsors and signature counts), but does not explicitly state read-only safety, authentication requirements, or rate limits. For a search tool this is adequate but leaves some gaps.

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

Conciseness4/5

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

The description is front-loaded and structured into purpose, usage, Args, and Returns sections. It is appropriately sized for 10 parameters, though there is minor redundancy: return contents are mentioned in the opening line and again in the Returns section.

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?

Given 10 parameters, no annotations, and an output schema, the description covers all inputs thoroughly and need not explain return values. However, with no annotations it could do more to state safety or authentication context, and it does not clarify what happens when no filters are supplied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description fully compensates by documenting all 10 parameters. It supplies formats (YYYY-MM-DD), allowed values (statuses, order_by), default behavior for take/skip, and clarifies member_id vs include_sponsored_by_member.

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 ('Search EDMs by topic'), then expands the domain with concrete EDM types (backbench motions, MP opinions, prayers against SIs). The 'See also' line names the closest sibling tools, so an agent can distinguish this search tool from get_early_day_motion, edms_for_member_id, and get_recently_tabled_edms without opening the 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?

Provides clear usage contexts: finding motions on specific issues, by member, or withdrawn motions. It also names alternatives in the 'See also' line, but does not specify the conditions under which each alternative should be preferred over this tool, and gives no explicit when-not guidance.

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

Deploy Server