Skip to main content
Glama

get_session_schedule

Read-onlyIdempotent

Retrieve upcoming and recent Swiss federal parliament sessions with a configurable limit of up to 20 to track parliamentary schedules.

Instructions

Upcoming and recent federal parliament sessions

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
limitNomax 20

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.0
    • addedInput schema / properties / limit / default
      Added value: +5
    • changedInput schema / properties / limit / description
      Previous value: -"Number of sessions to return (default: 5, max: 20)"New value: +"max 20"
  2. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is fully covered. The description adds nothing beyond them and leaves real behavioral ambiguity: the time window behind "upcoming and recent" is undefined, as is whether the limit applies to future sessions, past sessions, or the combined list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short phrase with no wasted words, but it errs toward under-specification rather than efficient front-loading. There is no structure at all — no second sentence to clarify ordering or window.

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

Completeness2/5

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

For a read-only list tool with no output schema, the description should at least say what a session entry contains and what "recent" means in time. Neither is present, so an agent cannot predict whether the result is useful for a given query without calling it.

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

Parameters3/5

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

Schema description coverage is 100% (the single limit parameter is documented as default 5, max 20), so the baseline of 3 applies. The description never mentions the limit or what it counts, so it adds no meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Upcoming and recent federal parliament sessions" identifies the resource clearly, but it is a noun phrase with no explicit verb and no scope detail (Swiss federal parliament? cantonal?). It does not differentiate from nearby siblings such as get_committee_meetings or search_parliament_business, which an agent could plausibly confuse it with.

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 when-to-use guidance, no exclusions, and no pointer to an alternative for related needs like committee meetings or parliamentary documents. The agent must infer from the name alone that this is the right tool.

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