Skip to main content
Glama
paulieb89

UK Legal Research MCP Server

Search Parliamentary Committees

committees_search_committees
Read-onlyIdempotent

Find UK parliamentary select committees by name, house, or active status. Returns summaries with IDs for retrieving membership or evidence.

Instructions

USE THIS TOOL WHEN searching or listing UK parliamentary select committees by name, house, or active status.

Returns committee summaries (name, house, active status, ID). AFTER calling, pass committee_id into committees_get_committee for current membership, or into committees_search_evidence to retrieve oral and written evidence submitted to that committee.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYesCommitteeSearchInput.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoName substring filter applied, or None
houseNoHouse filter applied, or None
active_onlyYesWhether results were restricted to currently active committees
totalYesNumber of committees returned in this call
committeesNoMatching committees. Use committees_get_committee for membership detail.
Behavior4/5

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

Annotations already provide read-only, non-destructive, idempotent hints. Description adds details on return fields and downstream capabilities, enhancing transparency.

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, front-loaded with usage instruction, no wasted words. Effortlessly scannable.

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 present and clear description of return values plus guidance on subsequent steps, the description fully covers what an agent needs.

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 already documents all parameters adequately. Description adds minimal extra meaning beyond what the schema provides.

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?

Description explicitly states verb+resource ('searching or listing UK parliamentary select committees') and scope (by name, house, active status). It distinguishes from siblings like committees_get_committee and committees_search_evidence.

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

Usage Guidelines4/5

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

Explicitly states when to use ('USE THIS TOOL WHEN searching or listing') and provides step-by-step guidance on using results with other tools. Could be improved by explicitly noting when not to use.

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