get_constituency_representations

Retrieve every MP who has represented a UK constituency over time, including dates and member details. Use it to research historical constituency representation by ID.

Instructions

Get all MP representations for a constituency over time | constituency history, who represented, past MPs | Use when researching which MPs have represented a constituency historically | Returns list of representations with dates and member details See also: get_my_mp, get_constituency_by_id.

    Args:
        constituency_id: Unique constituency ID number.

    Returns:
        List of representations with member details and date ranges.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`constituency_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

A3.9/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 does disclose the temporal scope ('over time') and the return shape ('list of representations with dates and member details'), but says nothing about authentication, rate limits, pagination, or result ordering for what is presumably a historical list.

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, synonyms, usage trigger, return summary and related tools are all front-loaded in the first block, and the Args/Returns sections are short. The pipe-delimited packing is dense but wastes no sentences.

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 simple one-parameter lookup with an output schema already defined, the description covers purpose, usage, parameter meaning and a return summary, and routes to related tools. Only the absence of any guidance on sourcing constituency_id and on pagination/limits keeps it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 for the single parameter. It adds that constituency_id is a 'Unique constituency ID number', which is marginally useful, but does not tell the agent where to obtain that ID (only implying it via the get_constituency_by_id cross-reference).

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?

The description states a specific verb and resource ('Get all MP representations for a constituency over time') and immediately scopes it with search-friendly synonyms ('constituency history, who represented, past MPs'). It also names related tools (get_my_mp, get_constituency_by_id), so it is clearly distinguishable from siblings like get_constituencies or get_constituency_latest_election.

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?

It gives an explicit trigger ('Use when researching which MPs have represented a constituency historically') and points to two alternatives/companions. There is no explicit when-not or a statement of what to use for current representation, so it falls just short of a full routing rule.

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

Deploy Server

UK Parliament MCP Server