Skip to main content
Glama
UK Parliament MCP Server

UK Parliament MCP Server

get_lords_journal_sittings

Retrieve Lords Journal sittings for a specific date and content type, including minutes, attendance, papers, appendix, or divisions, to read what was recorded for that sitting.

Instructions

Get Lords Journal content for a sitting date | minutes of proceedings, attendance, papers laid, appendix, divisions | Use to read what the Journal records for a Lords sitting | Returns sittings with the requested content. See also: get_lords_journal_content_dates.

    Args:
        sitting_date: Sitting date (YYYY-MM-DD).
        content_type: One of Attendance, MinutesOfProceedings, Papers, Appendix, Divisions.

    Returns:
        Journal sittings for the date and content type.
    

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": {
      "sitting_date": "<sitting_date>",
      "content_type": "<content_type>"
    },
    "name": "get_lords_journal_sittings"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_typeYes
sitting_dateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.19.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It does state that the tool returns sittings for the requested date and content type, which is useful, but it omits details such as read-only semantics, error behavior when no sitting exists, or pagination/return-shape traits beyond what the output schema provides.

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 reasonably front-loaded and structured, with purpose, usage, related tool, args, and returns. It repeats the content-type list in both the opening line and the Args section, which is slightly redundant but not harmful.

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, output schema, and two required parameters, the description covers the essential calling information. It could be richer about edge cases or the exact relationship to get_lords_journal_content_dates, but no critical decision input is missing.

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 fully compensate. It does: sitting_date is explicitly documented as YYYY-MM-DD, and content_type is documented with the exact allowed values (Attendance, MinutesOfProceedings, Papers, Appendix, Divisions).

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 uses a specific verb and resource ('Get Lords Journal content') and enumerates the relevant content types, making the tool's scope immediately distinguishable from siblings. It also names the closely related tool get_lords_journal_content_dates, so an agent can tell the two apart.

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 a clear use case ('Use to read what the Journal records for a Lords sitting') and points to a related alternative via 'See also'. However, it does not state when to choose this tool over get_lords_journal_content_dates or any when-not conditions.

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