Skip to main content
Glama
paulieb89

UK Legal Research MCP Server

Get Division Detail

votes_get_division
Read-onlyIdempotent

Retrieve complete details of a UK parliamentary division, including voting records of each member, with accurate total counts.

Instructions

Get full detail for a parliamentary division including how each member voted.

Voter lists are truncated to 100 per side to fit response limits. Total voter counts are always accurate regardless of truncation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYesDivisionDetailInput with division_id and house.

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
Behavior4/5

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

The description discloses voter list truncation to 100 per side and that total counts remain accurate, adding value beyond annotations which declare readOnlyHint, idempotentHint, and openWorldHint. No contradiction.

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?

Three sentences, no wasted words. Purpose is front-loaded, and every sentence adds value.

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?

Given the tool has an output schema and moderate complexity, the description covers purpose and key behavioral constraints (truncation, accuracy). Complete enough for an agent.

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 100%; the description does not add extra meaning beyond what the schema provides. Baseline 3 is appropriate.

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 gets full detail for a parliamentary division and how each member voted, using a specific verb and resource. It distinguishes from siblings like votes_search_divisions.

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 description implies usage after searching divisions but does not explicitly state when to use or when not, nor name alternatives. No exclusions or context beyond the basic purpose.

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