Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Nachrichten zu Abgeordneten und Themen

get_news
Read-onlyIdempotent

Liefert aktuelle parlamentarische Nachrichten aus RSS-Feeds. Abdeckung: Deutschland (Bundestag, Bundesrat, Wahlkreise) und Österreich (Nationalrat, Bundesrat, APA-OTS Presseaussendungen). Jeder Treffer nennt am Ende der Antwort seine Beleg-Seite und das Original. Gib beide Links an und zitiere mit dem Titel des Treffers. [🤖 KI-Einsatz (KLASSIFIZIERT, Claude Haiku 4.5): Bei EU-Rechtsakten (EUR-Lex-Radar) sind Kurzzusammenfassung und Relevanzwert maschinell erzeugt; Titel, Datum und Quell-Link stammen unverändert aus dem amtlichen Feed.]

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_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoZeitraum in Tagen. Standard: 7
limitNoAnzahl Artikel. Standard: 5
topicNoOptional: Thema zum Filtern
channelNoKanal — Deutschland: 'BUNDESTAG', 'BUNDESRAT', 'WAHLKREIS_DUISBURG' (Beispiel). Österreich: 'AT_NATIONALRAT', 'AT_BUNDESRAT', 'SALZBURG'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive), so the description's job is to add provenance behavior — and it does: every hit appends its Beleg-Seite and Original link, and the disclosure explains that for EUR-Lex-Radar EU acts the summary and relevance score are machine-generated while title/date/source link stay from the official feed. That machine-generation caveat is genuinely useful context an agent cannot get from annotations. It stops short of describing the response shape or how many feeds are queried per call.

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?

Well front-loaded: purpose first, then coverage, then citation rules, then the AI-disclosure block. The bracketed disclosure is verbose and heavily decorated ("🤖 KI-Einsatz (KLASSIFIZIERT, Claude Haiku 4.5)") but it carries real information, so it earns most of its length.

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 zero required params, no output schema, and a fully documented schema, the description covers the essentials: what is returned, where it is sourced from, how to cite it, and the machine-generated caveat for EU acts. Minor gaps remain on ordering/relevance (the description mentions a Relevanzwert for EU acts but not how results are ranked) and on whether the two country corpora can be mixed in one call.

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 the schema already documents days, limit, topic and channel including example channel values. The description restates the geographic meaning of the channels (Deutschland vs. Österreich) but adds no format, interaction, or defaulting detail beyond what the schema provides. Baseline 3 is correct here.

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?

"Liefert aktuelle parlamentarische Nachrichten aus RSS-Feeds" names a specific verb (liefert) and resource (Nachrichten), then enumerates the coverage scope (Deutschland: Bundestag/Bundesrat/Wahlkreise; Österreich: Nationalrat/Bundesrat/APA-OTS). An agent can immediately tell this is the retrieval tool for raw news items, distinct from the analytical siblings like get_mdb_profile or get_coalition_score.

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?

The description supplies output-handling instructions ("Gib beide Links an und zitiere mit dem Titel des Treffers") and sketches the channel landscape, which implies when to reach for this tool. However, it never states when NOT to use it or points to any alternative tool for related needs, leaving the use-vs-alternative decision to inference.

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.