get_constituencies

Search and list UK parliamentary constituencies by partial name with pagination to retrieve constituency data for lookup, mapping, or analysis.

Instructions

Search and list UK parliamentary constituencies | constituency search, find constituency, browse constituencies | Use when you need constituency information, want to search by name, or need constituency data for analysis | Returns list of UK parliamentary constituencies See also: get_my_mp, get_constituency_representations.

    Args:
        search_text: Optional filter by constituency name (partial match).
        skip: Number of constituencies to skip (for pagination).
        take: Number of constituencies to return (default 20, max 100).

    Returns:
        List of UK parliamentary constituencies.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`skip`	No
`take`	No
`search_text`	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

B3.4/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 burden. It does add real behavioral detail not in the schema: pagination via skip and a take default of 20 with a max of 100. However it omits permission requirements, ordering of results, and what search_text partial-matching actually matches.

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?

Front-loaded purpose is fine, but the pipe-separated keyword block ('constituency search, find constituency, browse constituencies') is low-value stuffing, and the purpose is restated in both the opening line and the 'Returns' line. Size is acceptable but not tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return format need not be explained, and the parameter descriptions are adequate. But with no annotations the description should say more about safe-read behavior or result ordering; it is adequate rather than complete.

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 carry the parameters, and it does: search_text is a partial name filter, skip is pagination offset, take is count with default 20 and max 100. These constraints (default/max) are genuinely added meaning beyond the bare 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 (search/list) and resource (UK parliamentary constituencies) clearly enough that an agent knows what it returns. It gestures at siblings via 'See also: get_my_mp, get_constituency_representations' but never explains how it differs from get_constituency_by_id or the other constituency tools, so differentiation is incomplete.

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?

The 'Use when you need constituency information, want to search by name, or need constituency data for analysis' clause gives a rough context, but it is generic and overlaps with many siblings. No explicit when-not or routing to alternatives like get_constituency_by_id for a known ID.

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