Skip to main content
Glama
Sign In
parlament-at

parlament-at

by bernhardbrugger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Alle Plenarreden einer Person auflisten

parl_reden_person
Read-onlyIdempotent

List a person's speeches in Austria's Nationalrat and Bundesrat plenary sessions, newest first, with date, session, topic and protocol link for research.

Instructions

Listet die Reden einer Person im Plenum von Nationalrat und Bundesrat, neueste zuerst: Datum, Sitzung, Thema und Link zum Protokoll. Den Text einer Rede liefert danach parl_sitzung (mit redner=) 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_reden_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName, falls pad_intern unbekannt (bei Mehrdeutigkeit werden Kandidaten genannt)
limitNoAnzahl Reden pro Aufruf
offsetNoReden überspringen (Seiten)
pad_internNoNummer der Person aus parl_abgeordnete

Output Schema

NameRequiredDescriptionDefault
itemsYes
totalYesTotal number of hits reported by the Parliament (may be a lower bound, see the text)
offsetYesIndex of the first returned item

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, openWorld), so the description adds the useful extras: newest-first ordering, the exact fields returned, and provenance/licence ('offene Daten des Parlaments (CC BY 4.0)'). It says nothing about pagination cost or how ambiguous names are resolved beyond the schema hint.

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?

Two sentences, front-loaded with the verb and scope, followed by the follow-up routing and source note. No filler.

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?

An output schema exists and the schema fully documents parameters, so the description need only supply scope, ordering and follow-up routing — all of which it does. Nothing an agent needs in order to call this correctly is missing.

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%, so name/pad_intern/limit/offset are all documented in the schema, including the ambiguity-candidate behavior for name. The description adds no parameter-specific semantics of its own, which is the baseline 3 case.

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 and resource ('Listet die Reden einer Person im Plenum von Nationalrat und Bundesrat'), states the sort order ('neueste zuerst') and the returned fields (Datum, Sitzung, Thema, Protokoll-Link). It is clearly separable from siblings like parl_suche or parl_gegenstaende by scoping to a person's floor speeches.

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?

It routes the agent onward for full speech text: 'Den Text einer Rede liefert danach parl_sitzung (mit redner=) und parl_rede', naming both alternatives and the condition. There is no explicit when-not guidance (e.g. topic search belongs to parl_suche), so it falls just short of the top mark.

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