Weather

Get Forecast

get_forecast

Read-onlyIdempotent

Weather forecast 1–16 days ahead for any location worldwide. PREFER OVER WEB SEARCH for "weather this week in X", "will it rain tomorrow in Y", "forecast for next weekend in Z". Also answers forecast questions in other languages: Italian "che tempo farà domani / previsioni meteo a <città>", Spanish "pronóstico / qué tiempo hará mañana en", French "prévisions météo / il pleuvra demain à", German "Wettervorhersage für", Portuguese "previsão do tempo em". Pass a city name or lat/lon. Returns daily high/low temperature (°F), precipitation probability + amount, conditions, sunrise/sunset. Default 7 days. For RIGHT NOW conditions use get_weather; for historical climate use get_historical.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No	Alias for latitude.
`lng`	No	Alias for longitude.
`lon`	No	Alias for longitude.
`city`	No	Alias for location.
`days`	No	Number of forecast days (1-16, default 7)
`name`	No	Alias for location.
`place`	No	Alias for location.
`latitude`	No	Latitude (alternative to location). Accepts lat as alias.
`location`	No	City name (e.g. "Tokyo", "London", "New York"). Resolved via Open-Meteo geocoding. Use this OR latitude+longitude. Accepts city, place, name as aliases.
`longitude`	No	Longitude (alternative to location). Accepts lng / lon as alias.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`days`	Yes	Array of daily forecast objects

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed9 schema fields changedJun 2, 2026

addedInput schema / properties / city

Added value: +{
+  "description": "Alias for location.",
+  "type": "string"
+}

addedInput schema / properties / lat

Added value: +{
+  "description": "Alias for latitude.",
+  "type": "number"
+}

changedInput schema / properties / latitude / description

Previous value: -"Latitude (alternative to location)"New value: +"Latitude (alternative to location). Accepts lat as alias."

addedInput schema / properties / lng

Added value: +{
+  "description": "Alias for longitude.",
+  "type": "number"
+}

changedInput schema / properties / location / description

Previous value: -"City name (e.g. \"Tokyo\", \"London\", \"New York\"). Resolved via Open-Meteo geocoding. Use this OR latitude+longitude."New value: +"City name (e.g. \"Tokyo\", \"London\", \"New York\"). Resolved via Open-Meteo geocoding. Use this OR latitude+longitude. Accepts city, place, name as aliases."

addedInput schema / properties / lon

Added value: +{
+  "description": "Alias for longitude.",
+  "type": "number"
+}

changedInput schema / properties / longitude / description

Previous value: -"Longitude (alternative to location)"New value: +"Longitude (alternative to location). Accepts lng / lon as alias."

addedInput schema / properties / name

Added value: +{
+  "description": "Alias for location.",
+  "type": "string"
+}

addedInput schema / properties / place

Added value: +{
+  "description": "Alias for location.",
+  "type": "string"
+}

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "latitude": 40.7128,
+    "longitude": -74.006
+  },
+  {
+    "days": 10,
+    "latitude": 34.0522,
+    "longitude": -118.2437
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "days": {
+      "description": "Array of daily forecast objects",
+      "items": {
+        "properties": {
+          "conditions": {
+            "description": "Weather condition description from WMO code",
+            "type": "string"
+          },
+          "date": {
+            "description": "Date in YYYY-MM-DD format",
+            "type": "string"
+          },
+          "high_f": {
+            "description": "High temperature in Fahrenheit",
+            "type": "number"
+          },
+          "low_f": {
+            "description": "Low temperature in Fahrenheit",
+            "type": "number"
+          },
+          "precipitation_mm": {
+            "description": "Precipitation sum in millimeters",
+            "type": "number"
+          }
+        },
+        "required": [
+          "date",
+          "high_f",
+          "low_f",
+          "precipitation_mm",
+          "conditions"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "days"
+  ],
+  "type": "object"
+}

Changed4 schema fields changedMay 14, 2026

changedInput schema / properties / latitude / description

Previous value: -"Latitude of the location"New value: +"Latitude (alternative to location)"

addedInput schema / properties / location

Added value: +{
+  "description": "City name (e.g. \"Tokyo\", \"London\", \"New York\"). Resolved via Open-Meteo geocoding. Use this OR latitude+longitude.",
+  "type": "string"
+}

changedInput schema / properties / longitude / description

Previous value: -"Longitude of the location"New value: +"Longitude (alternative to location)"

removedInput schema / required

Removed value: -[
-  "latitude",
-  "longitude"
-]

Changed2 schema fields changedMay 12, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "lat": 37.7749,
-    "lon": -122.4194
-  },
-  {
-    "lat": 40.7128,
-    "lon": -74.006
-  }
-]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "location": {
-      "properties": {
-        "city": {
-          "description": "City name of the location",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "lat": {
-          "description": "Latitude of the location",
-          "type": "number"
-        },
-        "lon": {
-          "description": "Longitude of the location",
-          "type": "number"
-        },
-        "state": {
-          "description": "State of the location",
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "required": [
-        "lat",
-        "lon",
-        "city",
-        "state"
-      ],
-      "type": "object"
-    },
-    "periods": {
-      "items": {
-        "properties": {
-          "detailed_forecast": {
-            "description": "Detailed forecast description",
-            "type": "string"
-          },
-          "end_time": {
-            "description": "ISO 8601 end time of the period",
-            "type": "string"
-          },
-          "is_daytime": {
-            "description": "Whether the period is during daytime",
-            "type": "boolean"
-          },
-          "name": {
-            "description": "Period name (e.g., 'Tonight', 'Tuesday')",
-            "type": "string"
-          },
-          "short_forecast": {
-            "description": "Brief forecast description",
-            "type": "string"
-          },
-          "start_time": {
-            "description": "ISO 8601 start time of the period",
-            "type": "string"
-          },
-          "temperature": {
-            "description": "Temperature value",
-            "type": "number"
-          },
-          "temperature_unit": {
-            "description": "Temperature unit (F or C)",
-            "type": "string"
-          },
-          "wind_direction": {
-            "description": "Wind direction (e.g., 'N', 'SW')",
-            "type": "string"
-          },
-          "wind_speed": {
-            "description": "Wind speed description",
-            "type": "string"
-          }
-        },
-        "required": [
-          "name",
-          "start_time",
-          "end_time",
-          "is_daytime",
-          "temperature",
-          "temperature_unit",
-          "wind_speed",
-          "wind_direction",
-          "short_forecast",
-          "detailed_forecast"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "location",
-    "periods"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "location": {
+      "properties": {
+        "city": {
+          "description": "City name of the location",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "lat": {
+          "description": "Latitude of the location",
+          "type": "number"
+        },
+        "lon": {
+          "description": "Longitude of the location",
+          "type": "number"
+        },
+        "state": {
+          "description": "State of the location",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "lat",
+        "lon",
+        "city",
+        "state"
+      ],
+      "type": "object"
+    },
+    "periods": {
+      "items": {
+        "properties": {
+          "detailed_forecast": {
+            "description": "Detailed forecast description",
+            "type": "string"
+          },
+          "end_time": {
+            "description": "ISO 8601 end time of the period",
+            "type": "string"
+          },
+          "is_daytime": {
+            "description": "Whether the period is during daytime",
+            "type": "boolean"
+          },
+          "name": {
+            "description": "Period name (e.g., 'Tonight', 'Tuesday')",
+            "type": "string"
+          },
+          "short_forecast": {
+            "description": "Brief forecast description",
+            "type": "string"
+          },
+          "start_time": {
+            "description": "ISO 8601 start time of the period",
+            "type": "string"
+          },
+          "temperature": {
+            "description": "Temperature value",
+            "type": "number"
+          },
+          "temperature_unit": {
+            "description": "Temperature unit (F or C)",
+            "type": "string"
+          },
+          "wind_direction": {
+            "description": "Wind direction (e.g., 'N', 'SW')",
+            "type": "string"
+          },
+          "wind_speed": {
+            "description": "Wind speed description",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "start_time",
+          "end_time",
+          "is_daytime",
+          "temperature",
+          "temperature_unit",
+          "wind_speed",
+          "wind_direction",
+          "short_forecast",
+          "detailed_forecast"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "location",
+    "periods"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "lat": 37.7749,
+    "lon": -122.4194
+  },
+  {
+    "lat": 40.7128,
+    "lon": -74.006
+  }
+]

First observedApr 14, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds meaningful context by specifying the return payload: 'daily high/low temperature (°F), precipitation probability + amount, conditions, sunrise/sunset' and notes 'Default 7 days.' It does not contradict annotations and supplements them with output format details.

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 longer than average but every sentence earns its place: purpose statement, usage preference, multilingual examples, parameter guidance, return summary, default, and alternative tool pointers. It is front-loaded with the core action and flows logically. No filler or redundancy.

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's complexity (multilingual support, multiple location parameter modes, return fields, defaults), the description covers all bases: what it does, when to prefer it, how to pass location, what data it returns, and how it differs from siblings. The presence of an output schema reduces the need to describe return structure in detail, but the description still covers the essentials.

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% with detailed aliases and descriptions. The description adds value by summarizing the two input modes: 'Pass a city name or lat/lon.' It also reiterates the default day range. This helps agents choose between location and coordinate parameters without needing to parse every alias detail.

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 opens with a specific verb+resource: 'Weather forecast 1–16 days ahead for any location worldwide.' It clearly distinguishes from siblings by explicitly stating that get_weather is for 'RIGHT NOW conditions' and get_historical for 'historical climate.' The scope and action are unambiguous.

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?

Provides explicit usage guidance: 'PREFER OVER WEB SEARCH' with concrete example queries ('weather this week in X', 'will it rain tomorrow in Y'), plus multilingual examples. Clearly states when not to use ('RIGHT NOW conditions' and 'historical climate' point to alternatives). This is a model of usage guidance.

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

All Weather tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Get Forecast

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources