Skip to main content
Glama

Parliament session schedule

get_session_schedule
Read-only

Retrieve recent and upcoming Federal Assembly sessions with dates and names, limited to a chosen count, so you can check parliamentary schedules.

Instructions

Recent and upcoming sessions of the Federal Assembly with dates and names.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_session_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds almost nothing beyond that: it does not say how 'recent' is bounded, whether results are date-ordered, or what happens when limit truncates the list, which matters since there is no output schema.

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?

One short sentence with the resource and temporal scope front-loaded; nothing is redundant. It is arguably under-specified rather than verbose, but structurally clean.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only lookup with one optional parameter and no output schema, the description covers the essentials of what is returned. It falls short on ordering, the definition of 'recent', and how the limit interacts with the result set.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single 'limit' parameter is never mentioned in the description. The name and default of 6 make its meaning guessable, but the description does not confirm that it caps the number of sessions returned or how truncation is handled.

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 names a specific resource ('sessions of the Federal Assembly') and its temporal scope ('recent and upcoming'), plus the fields returned ('dates and names'). It is clearly distinguishable from siblings like get_parliament_votes or get_parliament_business, though the verb is only implicit in the tool name.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no mention of alternatives such as get_parliament_business for agenda items, and no prerequisites. The only hint is the phrase 'recent and upcoming', which implies scheduling use but leaves selection between siblings to inference.

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