UK Parliament MCP Server

get_daily_reports

Retrieve daily summaries of UK Parliament written questions and answers for a date or range, filtered by Commons, Lords, or Bicameral, to track parliamentary question activity.

Instructions

Get daily reports of written questions and answers | daily reports, question reports, answer summaries, daily digest | Use for getting overview of parliamentary question activity on specific dates or date ranges | Returns daily reports with question and answer summaries

    Args:
        date_from: Start date for reports (YYYY-MM-DD).
        date_to: End date for reports (YYYY-MM-DD).
        house: Filter by house: 'Commons', 'Lords' or 'Bicameral' (1 or 2 also accepted).
        skip: Number of records to skip for pagination. Default: 0.
        take: Number of records to return. Default: 20.

    Returns:
        Daily reports with question and answer activity summaries.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`skip`	No
`take`	No
`house`	No
`date_to`	No
`date_from`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 6, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It discloses that the tool returns daily reports with summaries and lists pagination controls, but it never explicitly confirms read-only behavior, permission needs, or rate limits. The 'Get' verb implies a safe read, but that is left to inference.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and usage context, then lists arguments and return values in a standard structure. The pipe-separated keyword line is somewhat redundant, but the overall size and ordering are efficient.

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?

For a five-parameter read tool with an output schema, the description covers purpose, usage context, all parameter semantics, and a brief return summary. It lacks any note about read-only status or permissions, but the output schema means return values need not be explained further.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must document all five parameters, and it does so thoroughly: date formats (YYYY-MM-DD), accepted house values ('Commons', 'Lords', 'Bicameral' or 1/2), and pagination defaults (skip 0, take 20). This compensates fully for the empty schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Get daily reports of written questions and answers,' and adds that it gives an 'overview of parliamentary question activity.' This distinguishes it from individual question tools like search_written_questions, though it never explicitly names a sibling to avoid.

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?

It clearly says to 'Use for getting overview of parliamentary question activity on specific dates or date ranges,' giving a concrete context for when the tool applies. It does not state when not to use it or name alternative tools, so it stops 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.

Deploy Server