UK Parliament MCP Server

get_member_by_name

Search UK Parliament members by full or partial name to find MPs and Lords, check spellings, retrieve member IDs, and view party, constituency, and current status.

Instructions

Search for MPs and Lords by name with comprehensive member details | find MP, search politician, lookup member, who is, member search, parliamentary representative | Use for identifying members, checking spellings, finding member IDs, or getting basic member information | Returns member profiles with names, parties, constituencies, and current status See also: get_mp_profile, search_members, search_historical_members.

    Args:
        name: Full or partial name to search for. Examples: 'Boris Johnson', 'Keir Starmer', 'Smith'. Searches current and former members.

    Returns:
        Member profiles with names, parties, constituencies, and current status.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	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 behavioral burden. It discloses the search scope ('searches current and former members') and the returned fields, but says nothing about matching behavior (exact vs fuzzy), pagination, result limits, or behavior on ambiguous/multiple matches. For a read-only lookup that is a modest but real gap.

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 core sentences are front-loaded and useful, but the pipe-delimited keyword block ('find MP, search politician, lookup member, who is...') is SEO filler that adds no decision value, and the Returns section duplicates what the output schema already provides.

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 single-parameter search with an output schema present, the definition covers purpose, usage, argument semantics, and return fields adequately; return format need not be re-explained since an output schema exists. Missing only edge-case behavior for ambiguous or empty matches.

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 'name' accepts full or partial strings, gives concrete examples ('Boris Johnson', 'Keir Starmer', 'Smith'), and notes coverage of current and former members. It stops short of clarifying matching rules or multi-result handling.

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 ('Search for MPs and Lords by name') and immediately disambiguates scope as covering both current and former members. The 'See also' line names the nearest siblings (get_mp_profile, search_members, search_historical_members), so an agent can place it in the tool family without opening schemas.

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?

Explicitly lists the situations this tool serves: identifying members, checking spellings, finding member IDs, and getting basic member info. It names alternatives in the See-also line but does not state when NOT to use it (e.g. prefer search_members for broader queries, or get_member_by_id when the ID is already known).

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

Deploy Server