Skip to main content
Glama
Sign In
parlament-at

parlament-at

by bernhardbrugger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Verhandlungsgegenstand im Detail (Einbringer, Verlauf, Dokumente)

parl_gegenstand
Read-onlyIdempotent

Fetch details on Austrian National Council items like inquiries, bills, and petitions by citation and legislative period, including titles, submitters, history, and PDFs.

Instructions

Zeigt Details zu einem Gegenstand des Nationalrats: Anfragen ("7436/J"), Beantwortungen ("6209/AB"), Gesetzesvorlagen ("251/I"), Petitionen ("21/PET"), Bürgerinitiativen ("8/BI"): Titel, wer sie eingebracht bzw. beantwortet hat (mit Partei-Kürzel), Verlauf, PDF-Dokumente und Bezüge. Zitation und Gesetzgebungsperiode stehen in den Ergebnissen von parl_anfragen. 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": {
      "gp": "<gp>",
      "zitation": "<zitation>"
    },
    "name": "parl_gegenstand"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpYesGesetzgebungsperiode: 28 oder "XXVIII"
zitationYesNummer und Art, z. B. "7436/J" oder "6209/AB"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered structurally. The description adds useful context — the upstream open-data source and CC BY 4.0 license, plus what the payload contains (PDFs, Verlauf, Bezüge) — but says nothing about error behavior for invalid citations or missing Gegenstände.

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?

A single dense sentence front-loads the purpose, then the enumeration and the source note. Every clause carries information, though the type/citation examples and the license sentence make it slightly heavier than needed.

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 no output schema, the description carries the return-value burden and does so by naming the fields returned (Titel, Einbringer mit Partei-Kürzel, Verlauf, PDF-Dokumente, Bezüge). Combined with the prerequisite pointer to parl_anfragen, an agent has enough to call it 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 both parameters are documented in the schema. The description still adds value by mapping citation examples to object types ("7436/J" Anfrage, "6209/AB" Beantwortung, "251/I" Gesetzesvorlage, "21/PET", "8/BI"), which helps an agent construct a valid zitation.

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 ("Zeigt Details zu einem Gegenstand des Nationalrats") and enumerates the exact object types covered (Anfragen, Beantwortungen, Gesetzesvorlagen, Petitionen, Bürgerinitiativen) with example citation formats. This clearly separates it from the list-level sibling parl_gegenstaende.

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?

Explicitly tells the agent that Zitation and Gesetzgebungsperiode come from the results of parl_anfragen, which is actionable prerequisite guidance pointing at a sibling tool. It does not, however, contrast itself against parl_gegenstaende or say when a detail lookup is unnecessary.

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