Skip to main content
Glama
paulieb89

UK Legal Research MCP Server

Get Contributions In A Debate

parliament_get_debate_contributions
Read-onlyIdempotent

Retrieve verbatim contributions from a UK parliamentary debate by debate ID, optionally filtered to a specific member's speeches regardless of vocabulary.

Instructions

USE THIS TOOL WHEN you have a debate_ext_id and want verbatim contributions, optionally filtered to one member.

Canonical path for "everything a member said in this debate" regardless of vocabulary — text-search tools (parliament_member_debates, parliament_search_hansard) filter by contribution TEXT, dropping members who spoke without using your phrase verbatim. This tool filters by MemberId on the debate's Items list, so vocabulary doesn't matter.

Typical chain: parliament_find_member(name) → member_id, then parliament_search_hansard or parliament_lookup_by_column → debate_ext_id, then this tool. The parliament module's instructions describe the full composition pattern.

Without member_id, returns every contribution (~100-200 for a long debate).

If the wire returns no contributions for a member you expect to have spoken, report the empty result honestly — do NOT reconstruct quotes from training data. Authoritative source for member contributions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYesGetDebateContributionsInput with debate_ext_id (required) and optional member_id filter.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
member_idYesParliament Members API member ID
topicNoTopic phrase filter applied, if any
offsetNoSkip applied to this page
limitNoPage size requested
totalYesNumber of contributions returned in this call
has_moreNoTrue if a full page was returned (more may exist)
contributionsNoHansard contributions for the member. Each `text` field is capped at 3000 characters.
Behavior4/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description clarifies the tool's behavior on empty results and instructs honest reporting. It also mentions typical result size. This adds useful context, though annotations already cover safety.

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, front-loads the purpose, uses clear formatting (bold, bullet points), and every sentence adds value. No redundancy or wasted words.

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 output schema and annotations, the description completes the picture by covering purpose, usage alternatives, behavioral caveats, and parameter rationale. It is fully adequate for an agent to use correctly.

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 detailed descriptions for both parameters. The description adds extra context explaining why member_id is useful to avoid vocabulary filtering, enhancing understanding beyond 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?

The description clearly states it returns verbatim contributions from a debate, optionally filtered by member. It specifies the required debate_ext_id and contrasts with text-search tools, making the purpose unambiguous.

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 when to use this tool (when debate_ext_id is known and verbatim contributions are needed) and when not to rely on text-search tools. Provides a typical chain and warns against reconstructing quotes.

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