UK Parliament MCP Server

browse_locations

Explore UK Parliament locations by type and name to view the hierarchy of countries, regions, and constituencies. Returns parent and child locations matching your search.

Instructions

Browse locations by type and name, returning parent and child locations | location browse, constituency type, country region | Use when exploring the location hierarchy (e.g. countries, regions, constituencies) | Returns list of locations matching the type and name

    Args:
        location_type: Type of location (e.g. 'Constituency', 'Country', 'Region').
        location_name: Name of the location to browse.

    Returns:
        List of parent and child locations matching the criteria.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`location_name`	Yes
`location_type`	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.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden, and it does disclose the return shape (list of matching parent/child locations). However, it says nothing about read-only semantics, permissions, pagination, or result limits, which is a meaningful gap for a browse tool.

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 and useful, but the pipe-delimited keyword string ('location browse, constituency type, country region') is filler, and the 'Returns' line duplicates the opening sentence's return description.

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?

An output schema exists, so the description need not detail return values, and it covers both required parameters with examples plus the hierarchical scope. Adequate for a two-parameter browse tool; only behavioral caveats (limits, matching mode) are absent.

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: location_type is given concrete example values ('Constituency', 'Country', 'Region') and location_name is identified as the name to browse. The only omission is whether matching is exact or partial.

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 (browse) and resource (locations) and describes the return shape ('parent and child locations'). It is distinguishable from sibling location tools such as get_constituencies or get_calendar_locations, though it never names an alternative explicitly.

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?

'Use when exploring the location hierarchy (e.g. countries, regions, constituencies)' gives a clear triggering context. It stops short of stating when NOT to use it or which sibling to prefer for flat lookups, so it is clear but not exhaustive.

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

Deploy Server