parlament-at

Personen im österreichischen Parlament suchen

parl_abgeordnete

Read-onlyIdempotent

Search current and former Austrian Parliament members by name, body, function, club, or province, and filter results to current Nationalrat and Bundesrat members.

Instructions

Sucht Personen, die dem österreichischen Parlament angehört haben oder angehören (Nationalrat, Bundesrat, Bundesregierung u. a.), nach Name, Gremium, Funktion und - für aktuelle Mitglieder - Klub und Bundesland. Aktuelle Mitglieder von Nationalrat und Bundesrat sind markiert (mit Klub, Wahlkreis, Bundesland); nur_aktuell=true zeigt nur sie. Die Liste umfasst auch frühere Mitglieder, Regierungsmitglieder und Parlamentsbedienstete. Quelle: offene Daten des Parlaments (CC BY 4.0). Gremium-Kürzel: NR Nationalrat, BR Bundesrat, BuREG Bundesregierung, BV Bundesversammlung, MEP EU-Parlament, LH Landeshauptleute, KN/PN Konstituierende/Provisorische Nationalversammlung, MPO Mitglieder des Präsidiums/Ordnungsorgane.

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_abgeordnete"
  }
}

Input Schema

Name	Required	Description
`klub`	No	Klub/Fraktion eines aktuellen Mitglieds, z. B. SPÖ, FPÖ, NEOS, GRÜNE
`name`	No	Name oder Namensteile, ohne Titel, Groß-/Kleinschreibung und Umlaute egal
`limit`	No	Maximale Anzahl Treffer
`offset`	No	Treffer überspringen (für Seiten)
`gremium`	No	Gremium-Kürzel, z. B. NR, BR, BuREG
`kompakt`	No	Eine Zeile pro Treffer (Betreff gekürzt, Link bleibt) statt eines Blocks; spart Kontext bei langen Listen
`funktion`	No	Teil der Funktionsbezeichnung, z. B. "Bundesminister" oder "Klubobmann"
`bundesland`	No	Bundesland eines aktuellen Mitglieds, z. B. Wien oder Oberösterreich
`nur_aktuell`	No	Nur aktuelle Mitglieder von Nationalrat und Bundesrat

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

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so safety and idempotency are covered. The description adds useful behavioral context: the result set includes former members, government members, and parliamentary staff, current members are marked with club, constituency, and province, and the data source is parliamentary open data (CC BY 4.0). It does not discuss rate limits or authentication, but those are not implied by the annotations or tool type.

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 front-loaded with the core purpose and eligibility scope, followed by filter behavior and the Gremium code list. It is dense but all information is relevant for a 9-parameter search tool. The single long sentence is slightly run-on, but it does not waste space on repetition.

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?

Given 9 optional parameters, full schema coverage, an output schema, and read-only annotations, the description supplies the essential domain context: historical scope, current-member filtering, abbreviation decoding, and data licensing. It does not explain pagination or compact output, but those are documented in the schema. Completeness is strong though not exhaustive.

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 adds meaning beyond the schema by spelling out the full Gremium abbreviation list (NR, BR, BuREG, BV, MEP, LH, KN/PN, MPO) and by clarifying that klub and bundesland apply only to current members. This compensates for the fact that the schema itself only gives a few abbreviation examples.

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?

The description uses a specific verb ("Sucht") and resource ("Personen, die dem österreichischen Parlament angehört haben oder angehören") and scopes the search by several fields. It clearly defines the target population, including current and former members, government members, and parliamentary staff. It does not explicitly differentiate itself from sibling tools such as parl_person, so it falls short of a 5.

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

Usage Guidelines3/5

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

The description explains that nur_aktuell=true restricts results to current Nationalrat and Bundesrat members, and it notes which filters apply only to current members. However, it gives no explicit guidance on when to use this search tool versus alternatives like parl_person or parl_suche. Usage is implied rather than routed.

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

Deploy Server