dwd-mcp

dwd_current_weather

Retrieve current DWD ICON weather conditions for a German place, including temperature, humidity, apparent temperature, wind speed/direction, and general weather.

Instructions

Current DWD ICON conditions for a German place: temperature, humidity, apparent temperature, wind speed/direction, weather. place: e.g. "Berlin" or "Hamburg".

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

Input Schema

Name	Required	Description	Default
`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.5/5.0

Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral load. It does disclose the data source (DWD ICON) and the geographic restriction to German places, but says nothing about units, update cadence, or what happens when a place is not found or is outside Germany.

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?

Two short lines: the capability first, then the parameter hint. No filler, and the most important information is front-loaded. Minor redundancy with the schema's field list is negligible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the returned fields need not be explained, and the description correctly covers source and geographic scope. It still omits units, time resolution, and failure behavior for non-German or unrecognized places, which matter for correct invocation.

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 compensate; it does so by constraining the single parameter to a German place name and giving usable examples ("Berlin" or "Hamburg"). It stops short of describing matching behavior or fallback to the schema's Berlin 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 the concrete resource (current DWD ICON conditions) and enumerates the returned measurements: temperature, humidity, apparent temperature, wind speed/direction, weather. The word "current" distinguishes it from the sibling dwd_forecast, though 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?

The word "current" implies the when-to-use case (now-weather rather than prediction), but there is no explicit statement of when to prefer dwd_forecast or dwd_find_place, and no mention of prerequisites such as resolving an ambiguous place name first. Usage is inferable rather than stated.

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

Deploy Server