UK Parliament MCP Server

get_recently_tabled_edms

Fetch recently tabled Early Day Motions to monitor political sentiment, MP stances, and backbench activity. Returns titles, sponsors, supporters, and tabling dates.

Instructions

Get recently tabled Early Day Motions - formal political statements | EDMs, political motions, backbench initiatives, MP opinions, parliamentary statements, political positions, cross-party support | Use for tracking political sentiment, finding MP stances on issues, monitoring backbench activity, or researching political movements | Returns recent EDMs with titles, sponsors, supporters, and tabling dates | Data freshness: updated daily See also: search_early_day_motions.

    Args:
        take: Number of EDMs to return. Default: 10, recommended max: 50. Recent motions returned first.

    Returns:
        Recent EDMs with titles, sponsors, supporters, and tabling dates.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`take`	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.8/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 burden. It discloses useful behavior — data freshness (updated daily) and ordering (recent motions first) — but omits whether the call is read-only, pagination limits, or rate behavior. Adequate but with clear gaps for an unannotated tool.

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?

Front-loads the core purpose and constraints in the first paragraph, then separates Args/Returns. The pipe-separated keyword list ('EDMs, political motions, backbench initiatives, MP opinions...') is redundant noise, and the Returns line duplicates the output schema, costing a little 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?

An output schema exists, so return values needn't be re-explained, and the description still covers scope, freshness, and the single parameter's bounds. For a simple one-parameter read tool this is complete enough, missing only explicit alternative-routing detail.

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 explains that 'take' is the number of EDMs, gives the default (10) and a recommended max (50), and states recent motions are returned first. This meaningfully exceeds the bare schema, though the ordering note is somewhat redundant with the purpose text.

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+resource ('Get recently tabled Early Day Motions') with enough domain framing (sponsors, supporters, tabling dates) to know what is returned. It names a sibling (search_early_day_motions) via See also, but never explains how the two differ, so sibling differentiation is only partial.

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?

Offers concrete use cases ('tracking political sentiment, finding MP stances on issues, monitoring backbench activity') and points to an alternative via See also. However, it gives no explicit when-not or the condition that selects search_early_day_motions over this tool.

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

Deploy Server