Skip to main content
Glama
paulieb89

UK Legal Research MCP Server

Search Parliamentary Divisions

votes_search_divisions
Read-onlyIdempotent

Find UK Parliament vote summaries by topic, date, or member. Returns division title, date, vote counts, and pass/fail status. Combine with votes_get_division for detailed voter lists.

Instructions

USE THIS TOOL WHEN searching Commons or Lords formal votes by topic, date, or member.

Returns division summaries (title, date, vote counts, pass/fail). AFTER calling, pass division_id + house into votes_get_division for the full member-by-member voter lists.

Authoritative source for UK parliamentary vote records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch term for division titles, e.g. 'Rwanda' or 'Online Safety Bill'. Omit to browse recent divisions.
houseNoWhich house to search.Commons
from_dateNoStart date (YYYY-MM-DD).
to_dateNoEnd date (YYYY-MM-DD).
member_idNoFilter to divisions where this member voted. Get the member ID from parliament_find_member.
offsetNoNumber of divisions to skip before this page. Default 0. Re-call with offset=offset+returned while has_more is true.
limitNoMaximum divisions to return. Default 25 (Commons API max-per-page).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoThe search term, if any (None = browse recent)
houseYesCommons or Lords
offsetNoSkip applied to this page
limitNoPage size requested
totalYesNumber of divisions returned in this call
has_moreNoTrue if a full page was returned (more may exist)
divisionsNoMatching divisions. Use the integer `id` field with votes_get_division to fetch the full voter list.
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering safety. Description adds 'Authoritative source' but does not disclose pagination behavior or any additional behavioral nuances beyond what annotations provide.

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?

Four sentences, first sentence front-loaded with usage instruction. No wasted words, every sentence adds value.

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 full schema coverage, annotations, and an implied output schema, the description completes the picture by indicating the workflow (use with votes_get_division) and stating the source authority.

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%, so the schema fully documents all 7 parameters. The description adds a brief note on using after for full lists but no additional parameter-level meaning beyond what is in the schema.

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?

Clearly states the verb 'search' and resource 'Commons or Lords formal votes' with specific facets (topic, date, member). Distinct from sibling votes_get_division by noting that this tool returns summaries and the other provides detailed voter lists.

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?

Explicitly says 'USE THIS TOOL WHEN' and provides when-not-to-use by directing to votes_get_division for full lists, giving a clear workflow.

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