dwd-mcp

dwd_warnings

Fetches official German severe-weather warnings, sorted by newest and highest level, with filters for Bundesland and minimum warning level.

Instructions

Official DWD severe-weather warnings, newest/highest level first. state: filter by Bundesland — German name ("Bayern"), short code ("BY") or region substring ("Kassel"); empty = all of Germany. min_level: 1..4 (default 1).

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

Input Schema

Name	Required	Description	Default
`state`	No
`min_level`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations exist, so the description carries the burden. It usefully discloses the sort order (newest/highest level first) and the min_level default, which are real behavioral traits. It says nothing about result volume, pagination/caps, or the time window of 'warnings', leaving meaningful behavioral gaps for a no-annotation tool (mitigated by the presence of an output schema).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and ordering, then one tight line per parameter. No filler sentences and nothing duplicated that isn't needed to interpret the parameters.

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 two-parameter filter tool with an output schema, the description covers purpose, ordering, and both parameters thoroughly. The remaining gap is scope: it does not say whether warnings are currently active, upcoming, or how far ahead they extend, which an agent selecting between this and dwd_forecast would want.

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

Parameters5/5

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

Schema description coverage is 0% — the schema only shows anyOf[string, null] and an integer default — so the description must fully compensate, and it does. It names three accepted state formats with concrete examples ('Bayern', 'BY', 'Kassel' substring), defines empty as all of Germany, and gives the min_level range 1..4 with its default.

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?

States a specific resource and scope: 'Official DWD severe-weather warnings', plus an ordering guarantee ('newest/highest level first'). The domain is clearly distinct from dwd_current_weather, dwd_forecast or dwd_pollen, but the description never explicitly differentiates itself from those siblings.

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: an agent can infer this returns active severe-weather warnings, and the filter semantics are spelled out. There is no explicit when-to-use statement, no exclusion (e.g. 'for forecasts use dwd_forecast'), and no note on whether the result covers current warnings only.

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

Deploy Server