InfraNode

Weather

weather

Read-onlyIdempotent

Get current weather observations for a German city.

Sourced from the Deutscher Wetterdienst (DWD): temperature, wind, precipitation and related fields. Read-only, current conditions only (not a forecast). For warnings use get_city_resource(slug, resource='weather-warnings'). For a broader question about the city (not just weather) use get_city_overview instead, which already includes a live weather highlight.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	City identifier, e.g. 'berlin' or 'hamburg'. Resolved leniently: the German name with or without umlauts, any casing, a common English exonym or short form also works (München/munich/munchen -> muenchen, cologne -> koeln, frankfurt -> frankfurt-am-main). An unknown name returns 404 with a 'Meintest du ...?' suggestion. list_cities gives the canonical slugs.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 17, 2026
- addedOutput schema / $defs / ToolMeta / properties / note
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedJul 7, 2026

changedInput schema / properties / slug / description

Previous value: -"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."New value: +"City identifier, e.g. 'berlin' or 'hamburg'. Resolved leniently: the German name with or without umlauts, any casing, a common English exonym or short form also works (München/munich/munchen -> muenchen, cologne -> koeln, frankfurt -> frankfurt-am-main). An unknown name returns 404 with a 'Meintest du ...?' suggestion. list_cities gives the canonical slugs."

Changed12 schema fields changedJul 2, 2026
- removedInput schema / properties / slug / title
```
Removed value: -"Slug"
```
- removedInput schema / title
```
Removed value: -"weatherArguments"
```
- removedOutput schema / $defs / ToolMeta / description
```
Removed value: -"Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten."
```
- removedOutput schema / $defs / ToolMeta / properties / attribution / title
```
Removed value: -"Attribution"
```
- removedOutput schema / $defs / ToolMeta / properties / cache_status / title
```
Removed value: -"Cache Status"
```
- removedOutput schema / $defs / ToolMeta / properties / correlation_id / title
```
Removed value: -"Correlation Id"
```
- removedOutput schema / $defs / ToolMeta / properties / license / title
```
Removed value: -"License"
```
- removedOutput schema / $defs / ToolMeta / properties / source / title
```
Removed value: -"Source"
```
- removedOutput schema / $defs / ToolMeta / properties / source_status / title
```
Removed value: -"Source Status"
```
- removedOutput schema / $defs / ToolMeta / title
```
Removed value: -"ToolMeta"
```
- removedOutput schema / properties / data / title
```
Removed value: -"Data"
```
- removedOutput schema / title
```
Removed value: -"ToolEnvelope"
```

Changed2 schema fields changedJun 21, 2026

addedInput schema / properties / slug / description

Added value: +"City slug from the list_cities tool, e.g. 'berlin' or 'hamburg'."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "ToolMeta": {
+      "additionalProperties": true,
+      "description": "Envelope-Metadaten: Quelle, Status, Cache, Lizenz und Attribution.\n\nZusatzfelder (z.B. ``covered_cities``, ``radius_m`` bei partieller Abdeckung)\nbleiben dank ``extra=\"allow\"`` erhalten.",
+      "properties": {
+        "attribution": {
+          "title": "Attribution",
+          "type": "string"
+        },
+        "cache_status": {
+          "title": "Cache Status",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "license": {
+          "title": "License",
+          "type": "string"
+        },
+        "source": {
+          "title": "Source",
+          "type": "string"
+        },
+        "source_status": {
+          "title": "Source Status",
+          "type": "string"
+        }
+      },
+      "title": "ToolMeta",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "data": {
+      "title": "Data"
+    },
+    "meta": {
+      "$ref": "#/$defs/ToolMeta"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "title": "ToolEnvelope",
+  "type": "object"
+}

First observedJun 18, 2026

TDQS

A4.5/5.0

Behavior3/5

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

Annotations already provide strong behavioral cues: readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds value by confirming it's read-only and specifying 'current conditions only (not a forecast)', but doesn't elaborate on rate limits, response size, or any edge cases beyond what annotations imply. With such comprehensive annotations, the description's added behavioral context is moderate.

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?

The description is compact (three sentences), front-loads the core purpose in the first sentence, and uses clear, direct language. Every sentence serves a distinct purpose: defining the tool, clarifying scope, and providing usage guidance with alternatives. No wasted words.

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?

Given the tool has only one required parameter, comprehensive annotations, and an output schema (context signal), the description covers all essential aspects: purpose, data source, scope, and alternatives. It is fully adequate for an agent to decide when and how to invoke this tool correctly.

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%, meaning the `slug` parameter is well-documented in the schema itself. The description reinforces this with concrete examples and resolves leniency details (umlauts, English exonyms), which adds meaningful nuance beyond the schema's basic description. The extra context about error handling (404 with suggestion) further enriches parameter understanding.

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 clearly states the tool gets current weather observations for a German city, specifies the data source (Deutscher Wetterdienst) and the fields (temperature, wind, precipitation). It distinguishes this from a forecast tool, and the verb 'Get' combined with 'current weather observations' precisely describes the output.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool (for current weather) and provides concrete alternatives: for weather warnings use get_city_resource, for a broader city overview use get_city_overview. This clearly guides the agent away from misuse, especially given the sibling tools listed.

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

All InfraNode tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.