Skip to main content
Glama
paulieb89

UK Legal Research MCP Server

Search Hansard Debates

parliament_search_hansard
Read-onlyIdempotent

Search UK parliamentary debates and speeches in Hansard. Retrieve contributions from MPs and Lords with date, party, and text to understand legislative intent and political context.

Instructions

Search Hansard for parliamentary debates, questions, and speeches.

Returns contributions from MPs and Lords including date, party, debate title, and text (capped at 3000 chars per contribution). Useful for understanding legislative intent or political context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYesHansardSearchInput with query, optional date range, optional member filter.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe phrase that was searched in Hansard
from_dateNoStart date filter applied, if any
to_dateNoEnd date filter applied, if any
memberNoMember name filter applied, if any
offsetNoSkip applied to this page (Hansard API: skip)
limitNoPage size requested
totalYesNumber of contributions returned in this call
has_moreNoTrue if a full page was returned (more may exist; re-call with offset=offset+limit)
contributionsNoMatching Hansard contributions. Each `text` field is capped at 3000 characters.
Behavior4/5

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

Annotations (readOnlyHint, destructiveHint, idempotentHint) indicate safe, read-only behavior. The description adds value by specifying a 3000-character cap per contribution and listing return fields (date, party, debate title). No contradictions with annotations.

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?

Two sentences clearly convey purpose and usefulness without extraneous information. 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?

With an output schema (not shown), return values are documented. The description covers what is returned and the annotations handle behavioral aspects. For a search tool, this is complete.

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?

Input schema provides detailed descriptions for all 6 parameters (100% coverage). The description does not add significant meaning beyond the schema, except implicitly relating the query to the search scope. 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 verb 'Search' and the resource 'Hansard', and lists what is returned (debates, questions, speeches). It distinguishes from sibling tools like parliament_member_debates and parliament_search_petitions by specifying the scope of Hansard contributions.

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 mentions usefulness for 'understanding legislative intent or political context', but does not explicitly state when not to use this tool or suggest alternative sibling tools for specific cases (e.g., member-specific debates or petitions).

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