Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Umfrageschnitt

get_umfrage_schnitt
Read-onlyIdempotent

Gibt den aktuellen 14-Tage-Schnitt aller Bundestagsparteien aus Sonntagsfragen zurück — ungewichteter Mittelwert über die Institute, wobei je Institut nur die neueste Umfrage im Fenster zählt (keine Gewichtung nach Stichprobengröße oder Institut). Daten: dawum.de (ODbL). Ideal für Echtzeit-Stimmungsbilder in politischen Analysen. [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_umfrage_schnitt"
  }
}

Input Schema

NameRequiredDescriptionDefault
parteiNoOptional: Nur diese Partei zurückgeben, z. B. 'SPD', 'AfD', 'Grüne'

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 readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely useful behavior: the exact aggregation rule (unweighted mean, newest poll per institute only within the window) and the upstream data source with ODbL licensing, which an agent needs to interpret and cite the numbers.

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 sentence is front-loaded and dense with the information that matters (window, weighting, source). The trailing bracketed '[Ohne KI: ...]' line is promotional boilerplate that contributes little for an agent, but it does not obscure the definition.

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 single optional-parameter aggregation tool with no output schema, the description covers source, methodology, window and default scope. It stops short of describing the shape of the returned values (e.g. party-to-percentage mapping) and how parties without recent polls are handled.

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 the single optional 'partei' parameter is already documented with examples in the schema. The description only adds that the default is 'aller Bundestagsparteien', which lightly clarifies the no-argument case but adds no format or matching details.

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?

Names a precise resource and computation: a 14-day rolling average of Sonntagsfragen for all Bundestag parties. The methodological detail (one latest poll per institute, unweighted) distinguishes it implicitly from raw-poll siblings such as get_aktuelle_umfragen, but no sibling is named explicitly.

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?

'Ideal für Echtzeit-Stimmungsbilder in politischen Analysen' gives a use context but not a decision rule. There is no statement of when to prefer raw polls over this aggregate, or when not to use it, so the agent must infer routing from the methodology description.

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.