Skip to main content
Glama
UK Parliament MCP Server

UK Parliament MCP Server

get_lords_non_sitting_days

Lists House of Lords non-sitting days for a given month and year, helping you check whether the Lords sits on a specific date or during that period.

Instructions

List Lords non-sitting days in a month | recess, days the Lords does not sit, no business | Use to check whether the Lords sits on a given day or in a given month | Returns the non-sitting dates (MM-DD-YYYY). See also: get_lords_next_prev_business_days, get_non_sitting_days.

    Args:
        month: Month number (1-12).
        year: Year (e.g. 2025).
        data_source: 'Calendar' (default) or 'PublishedBusiness' to return days with no published business instead.

    Returns:
        List of non-sitting days in the month.
    

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "month": "<month>",
      "year": "<year>"
    },
    "name": "get_lords_non_sitting_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
monthYes
data_sourceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.19.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does reasonably well: it discloses the important data_source distinction ('Calendar' default vs 'PublishedBusiness' returning days with no published business) and the return date format. It stops short of stating read-only safety explicitly or any permission/rate-limit behavior, so not a 5.

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 definition is front-loaded with purpose and usage in its opening sentences, and the Args/Returns sections are compact. The pipe-delimited keyword list and the 'Returns: List of non-sitting days in the month' line partially restate the first sentence, adding a little redundancy.

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 read-only query tool with no annotations and an output schema, the description covers the core needs: purpose, usage context, all parameter semantics, return format, and sibling alternatives. It leaves only minor implicit details (e.g., explicit read-only nature) unstated.

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 fully: it does, documenting month range (1-12), a year example (2025), and the two accepted data_source values with their default and semantic difference. This is essential information absent from the raw 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?

The first sentence names a specific verb (List), resource (Lords non-sitting days), and scope (in a month). It then disambiguates with keywords ('recess, days the Lords does not sit, no business') and explicitly names sibling alternatives (get_lords_next_prev_business_days, get_non_sitting_days), so an agent can distinguish it without opening the schema.

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 gives clear usage context ('Use to check whether the Lords sits on a given day or in a given month') and points to two sibling tools via 'See also'. It doesn't state explicit exclusions or when those alternatives should be chosen instead, which keeps it below a 5.

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