UK Parliament MCP Server

get_member_bills

Retrieve bills an MP or Lord has sponsored or introduced. Returns the member summary and bill details with current stage, ordered by recent updates.

Instructions

Get the bills a member has sponsored | bills introduced by MP, Private Members' Bills, sponsored legislation, member's bills | Use when asked which bills an MP or Lord has introduced or sponsored | Returns the member and their sponsored bills with current stage, most recently updated first. Combines: get_member_by_id, search_bills (member filter). See also: get_bill_overview, get_bill_committees.

    Args:
        member_id: Parliament member ID. Get from get_member_by_name. Example: 4514
        take: Number of bills to return (default 20).

    Returns:
        Member summary, total sponsored bills and bill summaries.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`take`	No
`member_id`	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/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 the ordering behavior ('most recently updated first') and implies a read-only fetch, but says nothing about permissions, pagination limits, or exhaustiveness of the result. For a simple read this is adequate but thin.

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 sections are clean and front-loaded, but the opening pipe-delimited synonym list ('bills introduced by MP, Private Members' Bills, sponsored legislation, member's bills') is repetitive keyword padding that restates the same concept four ways.

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 brief Returns note is a bonus rather than a requirement. With both parameters documented and the scoping/ordering behavior stated, an agent has what it needs to call the tool correctly.

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: member_id is explained with its source (get_member_by_name) and a concrete example (4514), and take is defined with its default. This adds real meaning beyond the bare 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?

States a specific verb and resource ('Get the bills a member has sponsored') and expands scope with concrete synonyms (Private Members' Bills, sponsored legislation). An agent can distinguish it from search_bills or get_member_by_id without opening a 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?

'Use when asked which bills an MP or Lord has introduced or sponsored' gives a clear triggering condition, and it names related tools (get_bill_overview, get_bill_committees) plus the combination it wraps (get_member_by_id, search_bills). It lacks an explicit when-not or 'prefer X over this' statement, so it stops short of 5.

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

Deploy Server