Skip to main content
Glama
Sign In
parlament-at

parlament-at

by bernhardbrugger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Ausschüsse des Nationalrats oder Bundesrats

parl_ausschuesse
Read-onlyIdempotent

List Austrian Parliament committees for a legislative period and filter by name to retrieve chairs, responsibilities, recent agendas, and assigned items.

Instructions

Listet die Ausschüsse einer Gesetzgebungsperiode (Nationalrat: gp nötig, z. B. 28 oder "XXVIII"; Bundesrat: ohne gp). Mit suche= (Namensteil, z. B. "Finanz") eingegrenzt auf höchstens 3 Treffer zeigt es zusätzlich Vorsitz (Obleute mit Partei), Aufgabenbeschreibung, letzte Tagesordnungen und zugewiesene Gegenstände. 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_ausschuesse"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpNoGesetzgebungsperiode (Nationalrat)
sucheNoTeil des Ausschussnamens
gremiumNoNR = Nationalrat, BR = BundesratNR

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 read-only/idempotent/open-world safety, and the description adds the non-obvious enrichment behavior ('bei höchstens 3 Treffern zeigt es zusätzlich Vorsitz, Aufgabenbeschreibung, Tagesordnungen...') plus the data source and license. It does not discuss pagination or result ordering, keeping it below 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?

Purpose and body-type branching are front-loaded, then filtering semantics, then the enrichment payoff and source. Dense but every clause carries information; only the license/source tail could be considered optional.

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?

With three optional parameters and no output schema, the description must sketch return contents, and it does (names, chairs with party, task descriptions, agendas, assigned items). Enough to call correctly, though it omits the base record shape when no enrichment applies.

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, but the description adds value beyond the schema: the accepted gp formats ('28 oder "XXVIII"'), the NR/BR conditional for gp, and a concrete suche example ('Finanz') with the ≤3-hit threshold that the schema's maxLength does not convey.

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 specific verb and resource ('Listet die Ausschüsse einer Gesetzgebungsperiode') and immediately splits the two bodies with their differing requirements (Nationalrat needs gp, Bundesrat doesn't). An agent can distinguish this from parl_gegenstand or parl_sitzungen without opening any 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?

Gives concrete conditional guidance: gp is required for NR, omitted for BR, and suche narrows by name part. It also explains the consequence of a narrow search (enriched results at ≤3 hits). It stops short of naming when to prefer parl_gegenstand or parl_suche for related lookups.

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