Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Antwortverhalten Ministerien

get_ministry_responsiveness
Read-onlyIdempotent

Reaktionsfähigkeits-Index österreichischer Ministerien: Ø/Median-Antwortzeit auf Schriftliche Anfragen im Nationalrat, je Ministerium (Anfragen mit abgerufener Beantwortungsseite), dazu Antwortzeiten je Jahr seit 2017 über alle Ministerien: beantwortet, Median, P90, Anteil binnen 61 Tagen. Zeigt je Ministerium nur Ministerien mit mindestens einer beantworteten Anfrage im Datenbestand. [Ohne KI: liefert ausschließlich Originaldaten aus amtlichen Quellen.]

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": "get_ministry_responsiveness"
  }
}

Input Schema

NameRequiredDescriptionDefault
chamberNoOptional: 'NR' (Standard) oder 'BR'

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?

The supplied annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower, but the description still adds real value beyond them: it discloses the dataset's inclusion rule (only ministries with at least one answered inquiry), the temporal coverage since 2017, and the exact metric definitions. It does not describe the response shape or whether results are paginated, which is a real gap given there is no output schema.

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?

The core content is front-loaded in the first clause and the metric definitions follow logically; nearly every phrase carries information. The trailing bracketed provenance disclaimer ('Ohne KI: liefert ausschließlich Originaldaten aus amtlichen Quellen') is the only marginal sentence, and the single very long sentence would read better split.

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 burden of explaining what comes back, and it does define the two result dimensions (per-ministry aggregates and a per-year series). It stops short of describing the concrete response structure (e.g. whether these are two separate collections) and the BR chamber behaviour, which keeps it from being fully complete.

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?

There is a single optional parameter with 100% schema description coverage, so the schema already documents the chamber switch ('NR' default or 'BR'). The description mentions Nationalrat only and never explains what changes when 'BR' (Bundesrat) is requested, so it adds no meaning 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?

The description names a concrete resource and metric set: average/median response time of Austrian ministries to written Nationalrat inquiries, plus per-year series since 2017 with answered count, median, P90 and share within 61 days. This is far more specific than a restatement of the name. It does not, however, distinguish itself from the similarly named sibling get_commission_responsiveness, so an agent must still infer which corpus applies.

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?

Usage is only implied by the subject matter – an agent can infer this answers questions about ministry response latency, but there is no explicit when-to-use or when-not statement and no alternative tool is named. The scoping note ('only ministries with at least one answered inquiry') is a data-coverage caveat, not routing guidance.

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.