UK Parliament MCP Server

search_bills

Find UK parliamentary bills by title, subject, or keyword to research proposed legislation, track legislative progress, or filter by sponsoring member ID.

Instructions

Search for parliamentary bills by title, subject, or keyword. Use when researching proposed legislation, finding bills on specific topics, or tracking legislative progress. See also: get_bill_overview, get_recently_updated_bills, search_acts_of_parliament.

    Args:
        search_term: Search term for bill titles or content (e.g. 'environment', 'health', 'finance').
        member_id: Optional: member ID to filter bills sponsored by specific member.

    Returns:
        Matching bills with titles, stages, and sponsors.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`member_id`	No
`search_term`	Yes

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?

No annotations, so the description carries the full behavioral burden. It discloses the return shape ('matching bills with titles, stages, and sponsors') and the filter behavior, but says nothing about matching logic, pagination, result limits, or auth requirements. Adds some value but leaves meaningful behavioral 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?

Purpose and usage are front-loaded, then Args and Returns are cleanly separated. Slightly verbose with the structured Args/Returns formatting, but every line carries information and nothing is redundant.

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 Returns section is a bonus rather than a necessity. For a simple 2-param/1-required tool, the description covers purpose, usage, params, and returns; only pagination/result-limit behavior is missing.

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 coverage is 0%, so the description must compensate, and it does: search_term is defined as searching titles or content with concrete examples, and member_id is explained as an optional filter for sponsored bills. Both params gain meaning beyond the bare 'integer'/'string' schema types.

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?

Specific verb ('Search') plus clear resource ('parliamentary bills') and enumerated searchable dimensions ('by title, subject, or keyword'). It also names three sibling tools (get_bill_overview, get_recently_updated_bills, search_acts_of_parliament), giving the agent enough to route away from near-neighbors.

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?

Explicit 'Use when' clause covers three concrete scenarios (researching proposed legislation, finding bills on topics, tracking progress). It lists alternatives via 'See also' but gives no when-not or routing logic between them, so it stops short of a 5.

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

Deploy Server