UK Parliament MCP Server

get_recently_updated_bills

Track recent UK parliamentary bills and legislative updates by returning titles, stages, sponsors, dates, and current status for newly introduced or revised proposals.

Instructions

Get most recently updated bills and current legislative activity | recent bills, new legislation, latest laws, parliamentary bills, legislative updates, current proposals | Use for tracking new legislation, monitoring bill progress, or finding recently introduced/updated laws | Returns bill titles, stages, sponsors, dates, and current status | Data freshness: updated frequently See also: search_bills, get_bill_overview.

    Args:
        take: Number of bills to return. Default: 10, recommended max: 50. Higher numbers may slow response.

    Returns:
        Bill titles, stages, sponsors, dates, and current status.

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

A4.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It discloses the freshness model ('updated frequently') and roughly what is returned, but says nothing about auth needs, pagination, or whether the result set is bounded by recency window versus count. Adequate but incomplete for a read tool with a soft max parameter.

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 pipe-delimited purpose/keyword/usage line is front-loaded, but the synonym stuffing ('recent bills, new legislation, latest laws, parliamentary bills, legislative updates, current proposals') is redundant filler. The 'Returns' block also duplicates the existing output schema, repeating content the agent already has.

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 the description need not explain the return payload (its Returns line is redundant but harmless). For a single-parameter read tool it covers purpose, freshness, and the parameter caveat. Minor gaps remain around auth and pagination behavior.

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 coverage is 0%, so the description must do all the work, and it does: it defines 'take' as the number of bills, restates the default, adds a recommended max of 50, and warns that higher values slow the response. That is a real caveat the schema's bare integer type cannot convey.

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 ('Get most recently updated bills') with the scope qualifier 'most recently updated' that separates it from a paginated list. The 'See also' reference to search_bills and get_bill_overview lets an agent place it in context without opening either 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?

Gives concrete use cases ('tracking new legislation, monitoring bill progress, or finding recently introduced/updated laws') and names two alternatives. However, it never states when to prefer search_bills or get_bill_overview over this tool, so the routing decision is left implicit.

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

Deploy Server