Skip to main content
Glama
Sign In
UK Parliament MCP Server

UK Parliament MCP Server

by ChrisBrooksbank
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_lords_business_documents_for_date

Retrieve House of Lords business documents for a specific sitting day, including order paper PDFs and daily papers, with document filenames, type IDs, and DocumentForDayId values.

Instructions

List Lords business documents for a day | order paper PDF, HL business papers, daily documents | Use to find the published documents for a Lords sitting day | Returns document filenames, type ids and DocumentForDayId values. See also: get_lords_business_document.

    Args:
        day_date: Date to list documents for (YYYY-MM-DD).

    Returns:
        Documents published for the day.

Input Schema

NameRequiredDescriptionDefault
day_dateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.19.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden: it discloses that the operation is a list/read ('List'), describes the document types returned, and names return fields (filenames, type ids, DocumentForDayId values). It does not explicitly state read-only safety, side effects, or pagination behavior, but for a listing tool the disclosure is substantially informative.

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 core purpose is front-loaded in the first clause, and the pipe-separated segments keep related information together. The 'Returns' block is somewhat redundant because an output schema exists, but the description remains efficiently structured overall.

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?

Given the tool's simplicity and the presence of an output schema, the description supplies all necessary invocation context: purpose, scoping, parameter format, sibling alternative, and returned fields. It could be slightly more complete by explicitly stating that the operation is read-only and whether pagination applies, but no major gaps remain.

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 description coverage is 0%, so the description must compensate. It documents the single parameter with both its purpose ('Date to list documents for') and the expected format ('YYYY-MM-DD'), which is exactly the missing meaning an agent needs to invoke the tool correctly.

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 states a specific verb (List) and resource (Lords business documents for a day), and explicitly names the sibling it is not via 'See also: get_lords_business_document.' It also enumerates included document types (order paper PDF, HL business papers, daily documents), making the scope unambiguous.

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 explicitly says to use the tool 'to find the published documents for a Lords sitting day,' giving clear context. It also names the alternative tool (get_lords_business_document), but does not specify the exact conditions under which one should be chosen over the other, so it falls short of full when/when-not guidance.

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

Deploy Server

Other Tools