parlament-at

Plenarsitzungen von Nationalrat oder Bundesrat auflisten

parl_sitzungen

Read-onlyIdempotent

Lists Austrian National Council or Federal Council plenary sessions newest first, with date, type and link; filter by legislative period and paginate results.

Instructions

Listet Plenarsitzungen des Nationalrats (NR) oder Bundesrats (BR), neueste zuerst, mit Nummer, Datum, Art (Sitzung oder Zuweisungssitzung) und Link. Optional nach Gesetzgebungsperiode filtern (nur NR sinnvoll, z. B. 28 oder "XXVIII"). Für Tagesordnung, Redner und Reden einer bestimmten Sitzung: parl_sitzung und parl_rede. Quelle: offene Daten des Parlaments (CC BY 4.0).

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": "parl_sitzungen"
  }
}

Input Schema

Name	Required	Description	Default
`gp`	No	Gesetzgebungsperiode, nur für den Nationalrat
`limit`	No	Anzahl Sitzungen pro Aufruf
`offset`	No	Sitzungen überspringen (Seiten)
`gremium`	No	NR = Nationalrat, BR = Bundesrat	NR
`kompakt`	No	Eine Zeile pro Treffer (Betreff gekürzt, Link bleibt) statt eines Blocks; spart Kontext bei langen Listen

Output Schema

Name	Required	Description
`items`	Yes
`total`	Yes	Total number of hits reported by the Parliament (may be a lower bound, see the text)
`offset`	Yes	Index of the first returned item

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Oct 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds behavior beyond that: results come newest-first, gp is only sensible for NR, and the data source/license is named. It does not discuss pagination behavior across limit/offset, which keeps it from 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 most useful facts — what is listed, in what order, and what is returned — lead the description, followed by filtering caveats and sibling routing. It is dense but every clause carries operational information; the CC BY 4.0 attribution is the only element of marginal value to an agent.

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?

With an output schema present, the return values need not be re-explained, and annotations cover side effects, so the description is nearly complete: sorting, filtering scope and sibling delegation are all present. Only pagination semantics (default limit 10, offset paging) are left entirely to the schema.

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 description coverage is 100%, so the baseline is 3. The description exceeds that by explaining gp's semantics (legislative period, only relevant for the National Council) and giving concrete accepted formats (28 or "XXVIII"), which is meaning the schema's minLength/maxLength bounds do not convey.

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 names a specific verb+resource ("Listet Plenarsitzungen des Nationalrats (NR) oder Bundesrats (BR)") and even states the returned fields (Nummer, Datum, Art, Link) and default ordering. It explicitly distinguishes itself from parl_sitzung and parl_rede, so an agent can tell it apart from its siblings without opening a schema.

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

Usage Guidelines5/5

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

It states the filtering condition and its scope limitation (gp is only meaningful for NR, given as "28" or "XXVIII") and routes the agent elsewhere for per-session detail: "Für Tagesordnung, Redner und Reden einer bestimmten Sitzung: parl_sitzung und parl_rede." That is explicit when-to-use plus named alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server