Skip to main content
Glama
Sign In
parlament-at

parlament-at

by bernhardbrugger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Gesetzesvorlagen, Anträge, Volksbegehren, Petitionen und Bürgerinitiativen suchen

parl_gegenstaende
Read-onlyIdempotent

List Austrian National Council and Federal Council parliamentary items—government bills, motions, petitions, citizens' initiatives, or EU documents—filtered by legislative period and official keyword, newest first.

Instructions

Listet Verhandlungsgegenstände des Nationalrats oder Bundesrats, neueste zuerst: Regierungsvorlagen (RV), Anträge (ANTR), Volksbegehren (VOLKBG), Petitionen (PET), Bürgerinitiativen (BI) oder EU-Dokumente (EU). Filter: Gesetzgebungsperiode (gp) und amtliches Schlagwort (z. B. "Verwaltungsverfahren"; kein Volltext). Jeder Treffer hat eine Zitation wie "251/I"; damit zeigt parl_gegenstand den Stand im Verfahren (Ausschuss, Nationalrat, Bundesrat, Bundesgesetzblatt), Abstimmung und Dokumente. 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_gegenstaende"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpNoGesetzgebungsperiode: 28 oder "XXVIII"
artNoRV = Regierungsvorlage, ANTR = Antrag, VOLKBG = Volksbegehren, PET = Petition, BI = Bürgerinitiative, EU = EU-DokumentRV
limitNoAnzahl Treffer pro Aufruf
offsetNoTreffer überspringen (Seiten)
gremiumNoNR = Nationalrat, BR = BundesratNR
kompaktNoEine Zeile pro Treffer (Betreff gekürzt, Link bleibt) statt eines Blocks; spart Kontext bei langen Listen
schlagwortNoAmtliches Schlagwort, z. B. "Verwaltungsverfahren"

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.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the bar is lower; the description still adds genuinely useful traits: results are sorted newest-first, hits carry a citation like "251/I", and the data source/license is disclosed. It does not describe pagination limits beyond what the limit/offset params imply, which keeps it from a 5.

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?

Dense but front-loaded: what it lists, then sort order, then filters, then the follow-up tool, then provenance. Every clause carries information, though the enumeration of type abbreviations partially duplicates the enum and adds weight.

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, so return values need not be spelled out, yet the description still explains the citation field and where to resolve it. With 100% schema coverage and annotations covering the safety profile, an agent has everything needed to call this 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 the baseline is 3; the description earns above that by clarifying that schlagwort is an official keyword and explicitly NOT full-text, a distinction the schema field alone does not make. The remaining params (art, limit, offset, gremium, kompakt) are left entirely to the schema.

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 precise verb (listet) plus the resource (Verhandlungsgegenstände des Nationalrats oder Bundesrats) and enumerates the covered document types (RV, ANTR, VOLKBG, PET, BI, EU). It also explicitly distinguishes itself from the sibling detail tool parl_gegenstand, so an agent can route without opening either schema.

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 the two filtering axes (Gesetzgebungsperiode, amtliches Schlagwort) and warns that the keyword is not a full-text search, which implicitly steers full-text queries to parl_suche. The hand-off to parl_gegenstand for per-item status is explicit. It stops short of naming alternatives by name for the full-text case.

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