Skip to main content
Glama
paulieb89

UK Legal Research MCP Server

Get Division Detail

votes_get_division
Read-onlyIdempotent

Retrieve the full member-by-member voting record for a UK parliamentary division using its division ID and house. Total voter counts are always accurate, with voter lists limited to 100 per side per response.

Instructions

USE THIS TOOL WHEN you have a division_id + house and want the full member-by-member voting record.

Voter lists are truncated to 100 per side to fit response limits; total voter counts are always accurate regardless of truncation. Chain from votes_search_divisions or parliament_get_debate_divisions (which cross-resolves Hansard division refs into votes-API division_ids).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYesDivisionDetailInput.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDivision ID
titleYesDivision title / motion text
dateYesDate of the division
houseYesCommons or Lords
ayes_countYesTotal Aye votes
noes_countYesTotal No votes
passedYesWhether the motion passed
is_government_winNoWhether the government won (Lords only)
aye_votersNoMembers who voted Aye (may be truncated)
noe_votersNoMembers who voted No (may be truncated)
truncatedNoWhether voter lists were truncated to fit response limits
total_aye_votersNoTotal number of Aye voters before truncation
total_noe_votersNoTotal number of No voters before truncation
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint. The description adds crucial behavioral context: voter lists are truncated to 100 per side to fit response limits, but total voter counts are always accurate. This is additional transparency beyond annotations, with no contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (two sentences plus a parenthetical) and front-loaded with a clear usage directive ('USE THIS TOOL WHEN'). Every sentence adds necessary information without redundancy.

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

Completeness5/5

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

Given the presence of an output schema (which covers return values) and the annotations (which cover safety traits), the description completes the picture by explaining truncation behavior and chaining context from sibling tools. No additional behavioral or prerequisite information is needed for an agent.

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 coverage is 100% with descriptions for both parameters. The description adds value by clarifying the source of division_id ('from votes_search_divisions results') and noting that house defaults to 'Commons'. While the schema already covers the basics, this context improves clarity for an agent.

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 clearly states the tool's purpose: 'USE THIS TOOL WHEN you have a division_id + house and want the full member-by-member voting record.' It uses a specific verb ('get') and identifies the resource (division detail/voting record), and distinguishes from siblings by referencing chaining from votes_search_divisions or parliament_get_debate_divisions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly specifies when to use the tool (when you have division_id + house and want full voting record) and provides chaining context from other tools. It also warns about truncation of voter lists to 100 per side, which guides appropriate usage and sets expectations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/paulieb89/uk-legal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server