dwd-mcp

dwd_forecast

Retrieve DWD ICON weather forecasts for a German place, including current conditions, hourly details, and daily min/max, precipitation, wind, and sunrise/sunset for up to 7 days.

Instructions

DWD ICON-model forecast for a German place: current conditions, hourly (temperature, precipitation probability, wind, weather) and daily (min/max, precipitation probability, sunrise/sunset). place: e.g. "Berlin" or "München". days: 1..7 (default 3).

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

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

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; it discloses the underlying model (ICON), the temporal granularity of results, and the horizon bound. It omits units, behavior when a place cannot be resolved, and any latency/caching or rate-limit characteristics, which matter for an unannotated network-backed lookup.

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?

Four short lines, front-loaded with purpose then return content then parameter notes; every clause carries information and nothing is repeated from the schema title alone.

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, output-schema-backed tool with no annotations, the description covers source model, output shape, and both parameter semantics, which is close to sufficient. The remaining gap is failure handling for unresolvable places and the absence of any routing hint to sibling tools.

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 0%, so the description must supply the meaning: it gives a format example for 'place' ("Berlin" or "München") and an explicit range plus default for 'days' (1..7, default 3). Both parameters are covered, though it does not say what a non-matching place does or whether the day count includes today.

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 verb+resource ('DWD ICON-model forecast for a German place') and enumerates the returned sections (current conditions, hourly temperature/precipitation probability/wind/weather, daily min/max, sunrise/sunset). That enumeration implicitly separates it from dwd_current_weather, but no sibling is named explicitly, so the differentiation is left to inference.

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 implied rather than stated: 'for a German place' scopes the domain and 'days: 1..7 (default 3)' scopes the horizon. There is no explicit when-to-use/when-not guidance and no pointer to dwd_find_place for resolving ambiguous place names, nor to dwd_current_weather as a lighter alternative.

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

Deploy Server