Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Anfrage-Entwurf Nationalrat

generate_at_anfrage
Read-only

Entwirft eine 'Schriftliche Anfrage' für den österreichischen Nationalrat/Bundesrat zu einem Thema — gestützt auf thematisch ähnliche frühere Anfragen und einer Empfehlung, welcher Klub das Thema erfahrungsgemäß aufgreift. Professional/Enterprise Tier. [🤖 KI-Einsatz (ERZEUGT_LIVE, Claude Haiku 4.5): Der Anfragetext wird beim Aufruf maschinell verfasst — Entwurf, vor Einbringung fachlich prüfen.]

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": {
      "topic": "<topic>"
    },
    "name": "generate_at_anfrage"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesThema der Anfrage, z. B. 'Wartezeiten bei Facharztterminen in Salzburg'
chamberNoOptional: 'NR' (Nationalrat, Standard) oder 'BR' (Bundesrat)
mdb_nameNoOptional: Name der/des Abgeordneten, in deren Namen die Anfrage formuliert wird

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds genuinely non-obvious context on top: live AI generation (Claude Haiku 4.5), grounding in thematically similar past inquiries plus a club-recommendation heuristic, and a Professional/Enterprise tier gate. The one thing not disclosed is what the response actually contains or how long generation takes.

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?

Front-loaded with the core action and artifact, followed by grounding sources and tier, then a bracketed operational note. Two sentences and one bracket, all carrying information; the German phrasing is dense but not padded.

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?

For a 3-parameter generator with no output schema, the description covers what is produced, what it is grounded on, the tier requirement, and the human-review obligation. The remaining gap is return-shape/pagination-style information, which is minor given the tool emits a single draft.

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 topic, chamber ('NR'/'BR') and mdb_name are already documented. The description adds only indirect meaning — that chamber maps to Nationalrat vs. Bundesrat and that the draft is attributed to a named member — but no format or defaulting detail beyond the schema. Baseline 3 applies.

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?

States a specific verb ("Entwirft") and a specific artifact ("'Schriftliche Anfrage' für den österreichischen Nationalrat/Bundesrat") scoped to a topic, which is clearly distinguishable from a Stellungnahme-style sibling. It stops short of naming any sibling explicitly, so an agent must infer the contrast from the document type alone.

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?

Implied usage is clear (draft a parliamentary inquiry on a topic), and the bracket note adds a real workflow caution: the text is machine-generated live and must be professionally reviewed before submission. There is no explicit when-not guidance and no named alternative for cases where a different document type is wanted.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.