Skip to main content
Glama
paulieb89

UK Legal Research MCP Server

Search Committee Evidence

committees_search_evidence
Read-onlyIdempotent

Retrieve oral and written evidence submitted to a UK parliamentary committee using its committee ID. Supports pagination and type filtering.

Instructions

USE THIS TOOL WHEN you have a committee_id and want the oral and written evidence submitted to it.

Returns ONE PAGE of evidence (default 20). Free-text titles are capped per max_title_chars; witness lists are capped at 10 per item. For committees with many submissions, re-call with offset=offset+returned while has_more is true.

Authoritative source for parliamentary committee evidence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYesCommitteeEvidenceInput.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
committee_idYesCommittee ID this page belongs to
evidence_typeYesEvidence type filter applied to this query
offsetYesNumber of evidence items skipped before this page
limitYesMax evidence items requested for this page
returnedYesNumber of evidence items actually returned in this call
has_moreYesTrue if there may be more evidence beyond this page. Re-call with offset=offset+returned to fetch the next page. Conservative: when evidence_type='both', True if either oral or written upstream page came back full.
evidenceNoEvidence items in this page. Titles are capped per max_title_chars; witness lists are capped at 10 per item.
Behavior4/5

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

Beyond annotations (readOnlyHint, idempotentHint), description adds details on pagination (one page, default 20), caps on titles and witness lists, and authoritative claim. No contradictions.

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?

Description is extremely concise with no redundant information. Front-loaded key instruction, followed by pagination and cap details. 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?

For a paginated list tool with caps, the description fully covers usage. Output schema exists for return format, so no need to describe fields. Completeness is high.

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 already covers parameters with descriptions. The description adds meaningful context: 'max_title_chars' purpose and 'limit' splitting behavior when 'evidence_type=both', which enhances understanding beyond 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?

Description clearly states tool retrieves oral and written evidence for a given committee_id. It distinguishes from related tools like committees_search_committees and committees_get_committee by specifying the evidence focus.

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 states 'USE THIS TOOL WHEN you have a committee_id' and explains when to re-call for pagination. Provides clear context on usage limits and splitting behavior.

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