Skip to main content
Glama
paulieb89

UK Legal Research MCP Server

Search Parliamentary Committees

committees_search_committees
Read-onlyIdempotent

Search UK parliamentary select committees by name, house, or active status. Returns summaries for follow-up membership or evidence retrieval.

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
queryNoSearch term for committee names, e.g. 'defence' or 'treasury'. Filtered client-side against committee names. Omit to list all committees.
houseNoFilter by house.
active_onlyNoIf true, only return currently active committees.
limitNoMaximum committees to return. Default 100 comfortably covers all currently-active UK select committees. Raise only for historical sweeps.

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.
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds that it returns committee summaries (name, house, active status, ID) and hints at further usage, but this adds minimal new behavioral context beyond the 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?

The description is two focused sentences plus a follow-up line, all front-loaded with the core usage instruction. Every sentence adds value without redundancy.

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 an output schema, the description does not need to explain return values. It covers purpose, usage, and next steps sufficiently for a search/list tool with 4 optional parameters.

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 description coverage is 100%, so the baseline is 3. The description briefly mentions filters (name, house, active status) but does not add meaningful detail beyond what is already in the schema descriptions.

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 explicitly states 'USE THIS TOOL WHEN searching or listing UK parliamentary select committees' with specific filters (name, house, active status). It clearly distinguishes from siblings by mentioning the next steps of passing committee_id to committees_get_committee or 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?

The description provides explicit guidance on when to use the tool and what to do after (pass committee_id to related tools). However, it does not explicitly state when NOT to use this tool or list alternative tools, though siblings are provided separately.

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