UK Parliament MCP Server

get_constituency_election_result

Retrieve vote counts, winner, turnout, and candidate details for a specific UK constituency election by constituency and election ID.

Instructions

Get a specific election result for a constituency by election ID | constituency election, historic vote, election result | Use when you need a particular election result for a constituency | Returns vote counts, winner, turnout, and candidate details for that election

    Args:
        constituency_id: Unique constituency ID number.
        election_id: Election ID number.

    Returns:
        Election result with vote counts, winner, and turnout for the specified election.

Input Schema

TableJSON Schema

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

B3.2/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. The 'get' verb implies a read-only lookup and the description discloses the returned fields, but it says nothing about permissions, pagination, or whether a missing election returns an error or empty result.

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 sentence is front-loaded, but it is followed by pipe-separated keyword stuffing and an Args/Returns block that largely duplicates the schema and the opening sentence. Every element is readable but not all of it earns its place.

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 two-parameter lookup with an output schema, the description covers purpose, parameters, and return contents adequately. The main gap is the absence of any routing against the many similar election-result siblings.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description only restates the schema titles ('constituency_id: Unique constituency ID number', 'election_id: Election ID number'). It adds no format, range, or sourcing detail (e.g. where to obtain a valid election_id) to compensate for the undocumented 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 a specific election result for a constituency') and scopes it by election ID. However, it does not distinguish itself from the very similar sibling get_election_results_for_constituency, so an agent cannot tell the two apart from the description alone.

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 a particular election result for a constituency' restates the purpose rather than giving real guidance; no alternatives, prerequisites, or when-not conditions are named despite several near-duplicate siblings (get_election_results_for_constituency, get_constituency_latest_election, get_member_latest_election_result).

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

Deploy Server