UK Parliament MCP Server

get_committee_members

Retrieve members and staff of a UK Parliament committee by ID, including elected and lay members, with filters for current or former membership status.

Instructions

Get members and staff of a specific committee by committee ID. Use when you need to know who serves on a committee, their roles, and membership status (current/former). Returns both elected members and lay members.

    Args:
        committee_id: Committee ID to get members for.
        membership_status: Optional: filter by membership status (e.g. 'Current', 'Former').
        show_on_website_only: Show only members visible on website.
        skip: Number of records to skip (for pagination).
        take: Number of records to return (default 30, max 100).

    Returns:
        Members and staff of the committee.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`skip`	No
`take`	No
`committee_id`	Yes
`membership_status`	No
`show_on_website_only`	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.6/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 behavioral burden. It usefully discloses that both elected and lay members are returned, that membership status can be current or former, and that take defaults to 30 with a max of 100. It never states that the operation is read-only or mentions permission/auth requirements, so it is adequate but incomplete.

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 Args block is front-loaded and each parameter line earns its place, making the docstring scannable. The 'Returns: Members and staff of the committee' line is redundant given the tool has an output schema and merely restates the opening sentence.

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?

For a 5-parameter filtered getter with an output schema (so return shape needs no explanation) and no annotations, the description covers the filters, pagination, and population returned. The main omissions are the absence of any read-only assertion and any routing guidance against sibling member-listing tools.

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 largely does: all five parameters are documented, including examples for membership_status ('Current', 'Former'), the pagination role of skip, and the default (30) and ceiling (100) for take. It does not restate the default value of show_on_website_only, though that is present in the schema.

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 and resource: 'Get members and staff of a specific committee by committee ID.' It also scopes the output (elected members plus lay members, roles, current/former status). It does not differentiate from close siblings such as get_committee_staff or get_member_committee_memberships, which an agent could easily confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use when you need to know who serves on a committee, their roles, and membership status' gives implied usage context, which is better than nothing. However, it names no alternative tool and gives no exclusion conditions, even though get_committee_staff and get_member_committee_memberships overlap in scope.

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

Deploy Server