Skip to main content
Glama
Sign In
parlament-at

parlament-at

by bernhardbrugger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Eine einzelne Rede aus dem Plenarprotokoll lesen

parl_rede
Read-onlyIdempotent

Retrieves one speech from Austrian Parliament stenographic records by session and speech number, with paragraph ranges, interjection filtering, and offset pagination for long texts.

Instructions

Liefert den Text EINES Redebeitrags aus dem stenographischen Protokoll (Sitzung wie bei parl_sitzung, dazu die rede-Nummer aus deren Ergebnis). Zwischenrufe und Beifall stehen standardmäßig im Text; mit zwischenrufe=false werden sie weggelassen. Die Absätze sind in eckigen Klammern nummeriert: zum Zitieren die Absatznummer nennen, mit absaetze="5-9" nur diese Absätze holen. Lange Reden werden in Stücken von höchstens 45 000 Zeichen geliefert (offset zum Weiterlesen). Zitate immer mit Redner, Sitzung und der Quellangabe aus dem Ergebnis belegen. 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>",
      "rede": "<rede>"
    },
    "name": "parl_rede"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpNoGesetzgebungsperiode (nur Nationalrat)
redeYesNummer des Redebeitrags (rede=...) aus parl_sitzung
nummerYesSitzungsnummer
offsetNoAb diesem Zeichen weiterlesen
gremiumNoNR = Nationalrat, BR = BundesratNR
absaetzeNoNur diese Absätze, z. B. "7" oder "5-9" (die Nummern stehen in eckigen Klammern im Text); ersetzt das Blättern über offset
max_zeichenNoGröße des gelieferten Stücks
zwischenrufeNoZwischenrufe und Beifall mitliefern

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly, idempotent, and openWorld annotations, the description discloses non-obvious behavior: interjections and applause are included by default, zwischenrufe=false removes them, paragraphs are numbered for citation, absaetze selects specific paragraphs and replaces offset paging, and long speeches are chunked at 45,000 characters with offset continuation. It also states citation and source requirements.

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

Conciseness5/5

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

The description front-loads the core purpose and then packs each sentence with operational detail, including filtering, chunking, citation, and licensing. There is no redundant restatement of the name or schema fields.

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?

For an eight-parameter retrieval tool with no output schema, the description covers the essential calling context: how to obtain parameters, how content is chunked, how to filter paragraphs and interjections, and how to cite. The exact shape of the returned result remains defined by the tool output rather than the description, which is acceptable but leaves a small gap.

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 schema already documents all eight parameters. The description adds useful cross-parameter semantics: rede comes from parl_sitzung, zwischenrufe controls interjections/applause, absaetze uses paragraph numbers and replaces offset paging, and offset continues after the 45,000-character chunk limit.

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?

States a specific verb and resource: 'Liefert den Text EINES Redebeitrags aus dem stenographischen Protokoll', with the rede number coming from parl_sitzung. The purpose is clear, but it does not explicitly distinguish itself from sibling tools such as parl_reden_person.

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?

Explains that this tool is for reading one speech and that the required rede-Nummer comes from the result of parl_sitzung, giving clear usage context. It does not name alternatives or state when not to use it, so it falls short of full explicit when/when-not guidance.

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