Skip to main content
Glama
UK Parliament MCP Server

UK Parliament MCP Server

get_lords_business_sections_for_date

List the Lords business paper sections published for a specific date to see what is on the order paper that sitting day. Returns section IDs for further queries.

Instructions

List the Lords business sections published for a date | business paper contents, what is on the Lords order paper that day | Use to see which sections of the Lords business paper exist for a sitting day | Returns a list of section ids. See also: get_lords_business_sections, get_lords_business_section_data.

    Args:
        business_paper_date: Business paper date (YYYY-MM-DD).

    Returns:
        List of SectionId values published for the date.
    

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": {
      "business_paper_date": "<business_paper_date>"
    },
    "name": "get_lords_business_sections_for_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_paper_dateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.19.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool returns a list of section ids for a date, but omits explicit read-only assurance, error behavior, or rate limits; 'List' implies a read, but not stated.

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?

Front-loads the purpose and usage, but has redundancy: 'Returns a list of section ids' and 'Returns: List of SectionId values...' repeat the same information. The pipe-separated fragments are slightly awkward but readable.

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 one-parameter listing tool with an output schema, the description covers purpose, usage, parameter format, and related tools. It does not explain what a SectionId is or what to do if no sections exist, but that may be outside scope.

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 coverage is 0% (no property description), but the description supplies the parameter name, meaning, and format 'Business paper date (YYYY-MM-DD).' It could add whether the date must be a sitting day, though the usage note partially covers that context.

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?

States a specific verb (List) and resource (Lords business sections for a date), and clarifies it covers business paper contents. It names related tools but does not explicitly explain when to choose it over get_lords_business_sections, so sibling differentiation is incomplete.

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?

Provides a clear use case ('Use to see which sections of the Lords business paper exist for a sitting day') and names alternatives in 'See also'. It does not specify exclusions or conditions for selecting among the alternatives.

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