Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Klub-Stimmung Nationalrat

get_klub_sentiment
Read-onlyIdempotent

NÄHERUNG, KEINE OFFIZIELLE ABSTIMMUNG: LLM-geschätzte Stimmungswerte österreichischer Nationalrats-Klubs je Thema, basierend auf klassifizierten Redebeiträgen (nicht auf Einzelabstimmungen — Österreich veröffentlicht keine). Zeigt Stichprobengröße und Konfidenz je Wert. ACHTUNG Datenstand: Der Reden-Bestand hinkt der Gegenwart hinterher; jede Antwort weist das tatsächliche Bestandsende (letzte erfasste NR-Sitzung) aus — der Wert beschreibt den Stand bis dahin, nicht die aktuelle Debattenlage. [🤖 KI-Einsatz (KLASSIFIZIERT, Claude Haiku 4.5): Themenzuordnung und Stimmungswert je Rede sind maschinell vergeben — keine Abstimmungsdaten.]

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

Input Schema

NameRequiredDescriptionDefault
klubNoOptional: Klub/Fraktion, z. B. 'ÖVP', 'GRÜNE'
topicNoOptional: Thema, z. B. 'Klima & Umwelt'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds meaningful context beyond them: values are LLM-classified rather than vote-derived, each value carries sample size and confidence, and every response reports the actual inventory end date. That is solid disclosure, though it does not say how missing data or empty topics are handled.

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 most important caveat is front-loaded and the structure is logical (what it is, then data-lag warning, then AI disclaimer). There is some redundancy between the opening 'keine offizielle Abstimmung' and the later 'nicht auf Einzelabstimmungen', plus a partially duplicated AI note, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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-shape burden itself and does so: it states that sample size, confidence, and the inventory end date are included in each answer. For a two-optional-parameter read tool this leaves nothing an agent needs in order to call it correctly.

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 both optional parameters carry their own descriptions with examples ('ÖVP', 'Klima & Umwelt'). The description adds nothing about parameter meaning, so the baseline 3 applies — the schema does all the work.

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 resource (LLM-estimated sentiment values of Austrian National Council clubs per topic) and the underlying basis (classified speeches). The opening disclaimer 'NÄHERUNG, KEINE OFFIZIELLE ABSTIMMUNG' immediately establishes what kind of artifact this is, so an agent can tell it apart from vote-based siblings without inspecting any schema.

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 context is implied: it is for topic-level sentiment estimates, not individual votes, and the data-lag warning tells the agent when the output is unsuitable for current debate questions. However, no sibling tool is named and no explicit when-to-use/when-not rule is given, so the agent must infer alternatives on its own.

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.