Skip to main content
Glama

German voting-intention polls (Sonntagsfrage, DAWUM)

get_german_polls
Read-only

Free. Latest published poll of each institute in the last 35 days from DAWUM (open database, ODbL), with unweighted mean, minimum and maximum per party (CDU/CSU, AfD, SPD, Grüne, Linke, BSW, FDP, ...) and every poll with institute, date and sample size. Default Bundestag; optional parliament (e.g. Bayern). Stated voting intention in samples, not support among the whole population, no forecast, no seat or coalition projection. Attribution is in the response. Refreshed every 30 minutes.

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

Input Schema

NameRequiredDescriptionDefault
parliamentNoe.g. Bundestag (default), Bayern, Berlin

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only and open-world behavior, yet the description adds substantial context: free access, DAWUM as source under ODbL, a 35-day lookback window, a 30-minute refresh cadence, and in-response attribution. It also warns that figures are stated voting intention in samples rather than population support, which prevents misreading of results.

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 source, window, and output shape, and every clause carries information an agent would otherwise have to guess. The single dense paragraph of caveats could be split for scanability, but no sentence is filler.

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 must describe return contents, and it does: per-party mean/min/max, the party list, and per-poll institute/date/sample size, plus attribution. For a one-parameter read tool this is complete enough to call correctly and interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter already documents examples and the default, so the schema does the heavy lifting. The description reinforces the default ('Default Bundestag; optional parliament') but adds no new format or constraint information, making this a presentation win rather than added semantics.

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 resource ('Latest published poll of each institute in the last 35 days from DAWUM') and immediately scopes the output (unweighted mean/min/max per party plus each individual poll). No sibling tool covers German polling, so the topic alone separates it from the surrounding agent/data endpoints.

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 states the default scope ('Default Bundestag; optional parliament (e.g. Bayern)') and rules out what the tool is not for ('no forecast, no seat or coalition projection'), which tells an agent when a different data source would be needed. There is no explicit comparison to an alternative tool, but none of the listed siblings plausibly covers this data.

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.