get_last_sitting_date

Find the last sitting date for the Commons or Lords before a specified date, optionally including weekend sittings.

Instructions

Get last sitting date | previous sitting, last sat, before recess | Get the last sitting date prior to a specified date | Returns last sitting date

    Args:
        house: House: 'Commons' or 'Lords' (1 or 2 also accepted).
        date_to_check: Find last sitting date before this date (YYYY-MM-DD).
        include_weekend_sittings: Whether to include weekend sittings (default: false).

    Returns:
        Last sitting date prior to the specified date.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`house`	Yes
`date_to_check`	Yes
`include_weekend_sittings`	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

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses that weekend sittings are excluded by default via the include_weekend_sittings flag, which materially affects results. However, it says nothing about validation errors, behavior when no prior sitting date exists, or house-code handling, and 'Returns last sitting date' adds no behavioral detail.

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 alias phrase is front-loaded, which aids retrieval, and the Args/Returns structuring is easy to scan. It loses a point for mild redundancy - 'Get last sitting date' and 'Returns last sitting date' restate the same fact before any new information.

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 simple, well-bounded date lookup with a full output schema covering return values and complete parameter documentation, the description is nearly sufficient. The remaining gap is edge-case behavior (no date found, invalid house) which is not addressed.

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 compensate and it does: it documents all three parameters, giving accepted house values ('Commons' or 'Lords', 1 or 2 also accepted - important since the schema allows both int and string), the required date format (YYYY-MM-DD), and the default for the optional weekend flag.

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+resource and scope: 'Get the last sitting date prior to a specified date,' with useful search aliases ('previous sitting, last sat, before recess'). It is clear on its own, but it never distinguishes itself from the near-identical sibling 'get_hansard_last_sitting_date', leaving that routing ambiguity unresolved.

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

Usage Guidelines3/5

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

Usage is only implied through the scope phrase 'prior to a specified date,' which signals this is the backward-looking counterpart to get_next_sitting_date. There is no explicit when-to-use/when-not, no mention of the alternative tools (get_hansard_last_sitting_date, get_sitting_dates), and no stated prerequisites.

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

Deploy Server

UK Parliament MCP Server