dwd-mcp

dwd_pollen

Retrieve hourly and per-day maximum pollen counts by type for a German place, with forecasts covering 1 to 7 days.

Instructions

Pollen counts for a German place, by type (alder, birch, grass, mugwort, ragweed, olive) — hourly plus per-day maximum. NOTE: pollen data comes from CAMS via the Open-Meteo air-quality API, not from DWD. place: e.g. "Berlin". days: 1..7 (default 2).

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

Input Schema

Name	Required	Description	Default
`days`	No
`place`	No		Berlin

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a meaningful behavioral caveat: the data comes from CAMS via the Open-Meteo air-quality API, not DWD, which matters for provenance and trust. It also discloses the output shape (hourly plus per-day max) and the days range. It omits units, timezone, and whether non-German places fail or are coerced.

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?

Three tight sentences with no filler, and the core purpose is front-loaded. The provenance NOTE sits between the resource statement and the parameter guidance, which slightly interrupts the reading order, but nothing is redundant.

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?

An output schema exists, so return values needn't be detailed, and both parameters are explained despite zero schema coverage. For a simple two-parameter read tool this is nearly complete; only units, timezone, and error behavior for non-German places are left implicit.

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 description coverage is 0%, so the description must compensate, and it largely does: 'place: e.g. "Berlin"' clarifies that a city name is expected, and 'days: 1..7 (default 2)' supplies a range constraint absent from the schema (which has only a default, no min/max). It does not say what happens for out-of-range days or ambiguous place names.

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?

States a specific resource (pollen counts) with the exact breakdown (alder, birch, grass, mugwort, ragweed, olive) and output granularity (hourly plus per-day maximum). This is unmistakably distinct from the sibling weather, forecast, warnings, and health tools without needing to name them.

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: the pollen-type list and 'German place' scope suggest allergy/pollen queries, but there is no explicit when-to-use or when-not-to-use guidance, and no routing away from dwd_forecast or dwd_health for related questions. The parameter constraints (days 1..7) are the only operational guidance offered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server