UK Data for Agents

committee_search

Read-onlyIdempotent

Find a UK Parliament committee by name and get its id, house, type, parent committee, current sub-committees and contact email and address. This is the first step for the other committee tools and answers "which committee covers X" and "how do I contact it". Source: UK Parliament Committees API. Searches committee names only, not inquiry topics. (cost: 1 credit)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "committee_search"
  }
}

Input Schema

Name	Required	Description	Default
`q`	No	string, required, words from the committee name, e.g. "treasury"
`take`	No	integer, optional, how many committees to return (1-50), default 10

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, and the description adds genuinely non-structured facts: the upstream source (UK Parliament Committees API), the 1-credit cost, and the name-only search limitation. It omits result ordering and how partial matches are handled.

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?

Front-loads the verb, resource and return payload, then the routing role, then the scope caveat, then cost. Each sentence adds distinct information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully enumerates the returned fields (id, house, type, parent committee, sub-committees, contact details), which is exactly what an agent needs to chain into follow-on tools. Only match/pagination behavior is left implicit.

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 both q and take are already documented, and the description adds only light reinforcement ('by name', what fields come back) with no syntax or matching-behavior detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Find a UK Parliament committee by name') plus the returned fields, and draws an explicit boundary against topic-based search: 'Searches committee names only, not inquiry topics.' That boundary is what distinguishes it from siblings like committee_evidence_sessions.

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 positions the tool as 'the first step for the other committee tools' and gives the answerable questions ('which committee covers X', 'how do I contact it'). It does not name the specific follow-on tool or state what to do if name search fails, so it stops just short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All UK Data for Agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?