Skip to main content
Glama
Sign In
parlament-at

parlament-at

by bernhardbrugger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Verlauf einer Plenarsitzung: Tagesordnungspunkte und Redner

parl_sitzung
Read-onlyIdempotent

Retrieves National Council or Federal Council plenary sessions by number with times, protocol link, agenda items, and speeches (speaker, party, speech ID); filter by speaker or agenda topic.

Instructions

Zeigt eine Plenarsitzung des Nationalrats (gremium NR, gp und Sitzungsnummer) oder Bundesrats (gremium BR, Nummer): Beginn/Ende, Link zum gesamten Protokoll und den Verlauf mit Uhrzeit, Tagesordnungspunkten und - bei Debatten - allen Redebeiträgen mit Name, Partei und der Nummer (rede=...), die parl_rede braucht. Mit redner= (Name) zeigt es nur die Beiträge dieser Person, mit top= nur passende Tagesordnungspunkte. 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_sitzung"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpNoGesetzgebungsperiode (nur Nationalrat)
topNoNur Tagesordnungspunkte, deren Titel das enthält
nummerYesSitzungsnummer, z. B. 30
rednerNoNur Wortmeldungen dieser Person (Name oder Teil davon)
gremiumNoNR = Nationalrat, BR = BundesratNR

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare the operation as read-only, idempotent, and open-world. The description adds substantial behavioral detail beyond that: what the response contains (start/end, protocol link, timed agenda, all speeches with name/party/rede number) and how filtering changes the result set.

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 description is dense and front-loaded, leading with the core purpose and followed by filters and dependencies. It is somewhat long in a single paragraph, but every clause conveys concrete usage or output information.

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?

For a five-parameter lookup tool without an output schema, the description explains the required identifiers, filter behavior, return contents, and cross-tool dependencies. An agent has enough context to invoke it correctly and interpret the result.

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 the schema already documents all five parameters. The description still adds value by clarifying that gp applies only to the Nationalrat, the redner/top filters narrow speeches or agenda items, and the rede value is the identifier required by parl_rede.

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?

Starts with a specific verb and resource ('Zeigt eine Plenarsitzung des Nationalrats ... oder Bundesrats') and distinguishes the two chambers by their required identifiers. It also previews the returned content, so an agent can tell exactly what this tool is for versus sibling tools.

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?

Explicitly routes the agent to parl_sitzungen for session numbers and to parl_rede for the speech number returned here, and explains the local redner/top filters. It does not explicitly frame when to choose this over every other sibling, but the key dependencies and alternatives are named.

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