Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Stellungnahme-Entwurf Begutachtung

generate_at_stellungnahme
Read-only

Entwirft eine Stellungnahme im österreichischen Begutachtungsverfahren zu einem konkreten Ministerialentwurf, für eine benannte Institution (z. B. WKÖ, AK). Zuerst search_at_begutachtungen aufrufen, um die begutachtung_id zu ermitteln. Professional/Enterprise Tier. [🤖 KI-Einsatz (ERZEUGT_LIVE, Claude Haiku 4.5): Die Stellungnahme wird beim Aufruf maschinell verfasst — Entwurf, vor Einreichung 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": {
      "begutachtung_id": "<begutachtung_id>",
      "institution": "<institution>"
    },
    "name": "generate_at_stellungnahme"
  }
}

Input Schema

NameRequiredDescriptionDefault
positionNoOptional: die inhaltliche Position, z. B. 'grundsätzlich zustimmend, mit Änderungswünschen bei §3'
institutionYesInstitution im Namen derer die Stellungnahme verfasst wird, z. B. 'Wirtschaftskammer Österreich'
begutachtung_idYesID des Ministerialentwurfs, z. B. 'XXVIII_ME_47' — via search_at_begutachtungen ermitteln

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations, it discloses the key behavioral trait: the text is generated live at call time by a named model (Claude Haiku 4.5) and must be professionally reviewed before submission — which explains the non-idempotent hint and warns against treating output as authoritative. The generation claim does not conflict with readOnlyHint=true, since nothing indicates persistence or mutation, only in-memory text synthesis. It does not mention latency, cost, or output length, 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?

Front-loaded with the purpose, followed by the prerequisite call and the tier constraint, then a bracketed note on live AI generation. Each sentence carries distinct information, though the tier and model-detail clauses add a slightly operational, banner-like layer that could be tightened.

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?

There is no output schema, so the description must signal the return value; 'Entwurf, vor Einreichung fachlich prüfen' makes clear that a reviewable draft text comes back. Combined with the explicit ID-resolution prerequisite and the three documented parameters, an agent has enough to call it correctly, with only the draft's length/format left implicit.

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 coverage is 100% and every property already carries a description, including the note that begutachtung_id comes from search_at_begutachtungen. The description restates that provenance and adds institution examples (WKÖ, AK) and the notion of a substantive position, but adds no format or syntax detail beyond the schema. Baseline 3 is appropriate.

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?

The description names a specific verb and artifact ('Entwirft eine Stellungnahme') bounded to a precise domain and input ('im österreichischen Begutachtungsverfahren zu einem konkreten Ministerialentwurf, für eine benannte Institution'). The Austrian Begutachtungsverfahren / Ministerialentwurf framing distinguishes it from the EU-related and other generate/search siblings without needing to enumerate them.

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?

It gives an explicit prerequisite sequence: 'Zuerst search_at_begutachtungen aufrufen, um die begutachtung_id zu ermitteln', naming the sibling that must run first. It also gates access ('Professional/Enterprise Tier') and warns that the output is a draft to be checked before submission. It does not state a when-not condition, but the positive guidance is concrete enough to act on.

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.