Skip to main content
Glama
Sign In
parlament-at

parlament-at

by bernhardbrugger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Was wurde in einer Plenarsitzung beschlossen?

parl_beschluesse
Read-onlyIdempotent

Get per-agenda-item decisions and rejections from Austrian Nationalrat or Bundesrat plenary sessions, including party vote results and next steps. Filter by session, period, or agenda item.

Instructions

Zeigt zu einer Plenarsitzung des Nationalrats (gremium NR, gp, Sitzungsnummer) oder Bundesrats (BR) pro Tagesordnungspunkt, was beschlossen oder abgelehnt wurde, mit Abstimmungsergebnis nach Parteien (Dafür/Dagegen) und dem weiteren Weg (z. B. Bundesrat). Dazu Links zur Tagesordnung und zur Parlamentskorrespondenz. Mit top= (Teil des Titels oder "TOP 3") eingrenzen. Sitzungsnummern liefert parl_sitzungen. Quelle: offene Daten des Parlaments (CC BY 4.0).

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": {
      "nummer": "<nummer>"
    },
    "name": "parl_beschluesse"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpNoGesetzgebungsperiode (nur Nationalrat)
topNoNur passende Tagesordnungspunkte, z. B. "TOP 2" oder "Budget"
nummerYesSitzungsnummer, z. B. 30
gremiumNoNR = Nationalrat, BR = BundesratNR

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world behavior, so the description is not burdened by safety disclosure. It still adds real value beyond them: the shape of the result (vote breakdown by party, further path such as Bundesrat, links to Tagesordnung and Parlamentskorrespondenz) and the data source/license.

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?

Leading sentence front-loads what is returned and for whom; the remaining sentences carry distinct facts (top filter, session-number source, licensing). Slightly dense as one paragraph but nearly every clause earns its place.

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

Completeness5/5

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

No output schema exists, and the description compensates by describing the returned vote breakdown, procedural next step and links. Combined with full schema coverage on four parameters, an agent has everything needed to call it correctly.

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 100%, so baseline is 3; the description goes beyond it by explaining that top accepts either a title fragment or a "TOP 3" style string, that gp applies only to the Nationalrat, and that nummer comes from parl_sitzungen.

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?

States a specific verb+resource: returns per agenda item what was decided/rejected in a Nationalrat or Bundesrat plenary session, including per-party vote results and next steps. It explicitly distinguishes the two chambers and their parameter requirements, so it is clearly separable from siblings like parl_sitzungen or parl_gegenstand.

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?

Gives concrete usage context: use top= to narrow to part of a title or "TOP 3", and obtain Sitzungsnummern from parl_sitzungen. This is a clear routing hint to a sibling, though it doesn't state exclusions (e.g. when to prefer parl_gegenstand for a single item).

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