Weather

Get Historical

get_historical

Read-onlyIdempotent

AUTHORITATIVE historical daily weather for any location, back to 1940. Source: ERA5 reanalysis (ECMWF's global atmospheric reconstruction — the standard reference dataset for climate research). Pass a city or lat/lon + date range. Returns daily high/low temperature, precipitation, conditions. Defaults to the last 30 days if no dates given. Use for "what was the weather in X on date Y", climate baselines, comparing this year to historical averages, retrospective weather context for any event.

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.
`name`	No	Alias for location.
`place`	No	Alias for location.
`end_date`	No	End date YYYY-MM-DD (inclusive). Optional — defaults to today.
`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.
`start_date`	No	Start date YYYY-MM-DD (>= 1940-01-01). Optional — defaults to 30 days ago.

Output Schema

TableJSON Schema

Name	Required	Description
`days`	Yes	Array of historical daily entries
`country`	Yes	Country name from geocoding
`end_date`	Yes	End date (YYYY-MM-DD) used for query
`latitude`	Yes	Latitude coordinate
`location`	Yes	Resolved city name from geocoding
`longitude`	Yes	Longitude coordinate
`start_date`	Yes	Start date (YYYY-MM-DD) used for query

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: +[
+  {
+    "city": "Paris"
+  },
+  {
+    "end_date": "2023-12-31",
+    "latitude": 51.5074,
+    "longitude": -0.1278,
+    "start_date": "2023-01-01"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "country": {
+      "description": "Country name from geocoding",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "days": {
+      "description": "Array of historical daily entries",
+      "items": {
+        "properties": {
+          "conditions": {
+            "description": "Weather condition description or null if unavailable",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "date": {
+            "description": "ISO date string (YYYY-MM-DD)",
+            "type": "string"
+          },
+          "high_f": {
+            "description": "High temperature in Fahrenheit (null if unavailable)",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "low_f": {
+            "description": "Low temperature in Fahrenheit (null if unavailable)",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "precipitation_mm": {
+            "description": "Precipitation in millimeters (null if unavailable)",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "date",
+          "high_f",
+          "low_f",
+          "precipitation_mm",
+          "conditions"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "end_date": {
+      "description": "End date (YYYY-MM-DD) used for query",
+      "type": "string"
+    },
+    "latitude": {
+      "description": "Latitude coordinate",
+      "type": "number"
+    },
+    "location": {
+      "description": "Resolved city name from geocoding",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "longitude": {
+      "description": "Longitude coordinate",
+      "type": "number"
+    },
+    "start_date": {
+      "description": "Start date (YYYY-MM-DD) used for query",
+      "type": "string"
+    }
+  },
+  "required": [
+    "location",
+    "country",
+    "latitude",
+    "longitude",
+    "start_date",
+    "end_date",
+    "days"
+  ],
+  "type": "object"
+}

Changed6 schema fields changedMay 14, 2026

changedInput schema / properties / end_date / description

Previous value: -"End date YYYY-MM-DD (inclusive)"New value: +"End date YYYY-MM-DD (inclusive). Optional — defaults to today."

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)"

changedInput schema / properties / start_date / description

Previous value: -"Start date YYYY-MM-DD (>= 1940-01-01)"New value: +"Start date YYYY-MM-DD (>= 1940-01-01). Optional — defaults to 30 days ago."

removedInput schema / required

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

Changed2 schema fields changedMay 13, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "_apiKey": "your-metals-api-key",
-    "date": "2024-01-15"
-  },
-  {
-    "_apiKey": "your-metals-api-key",
-    "base": "GBP",
-    "date": "2023-06-30",
-    "symbols": "XAU,XCU"
-  }
-]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "base": {
-      "description": "Base currency code (e.g., USD, EUR)",
-      "type": "string"
-    },
-    "date": {
-      "description": "Historical date in YYYY-MM-DD format",
-      "type": "string"
-    },
-    "rates": {
-      "additionalProperties": {
-        "type": "number"
-      },
-      "description": "Metal spot prices per troy ounce, keyed by symbol (e.g., XAU, XAG)",
-      "type": "object"
-    },
-    "timestamp": {
-      "description": "Unix timestamp of when prices were captured",
-      "type": "number"
-    }
-  },
-  "required": [
-    "base",
-    "date",
-    "timestamp",
-    "rates"
-  ],
-  "type": "object"
-}New value: +null

AddedMay 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Given annotations already declare readOnlyHint=true and destructiveHint=false, the description adds valuable context beyond these: data source (ERA5 reanalysis), temporal reach (back to 1940), default date range (last 30 days), and output fields (daily high/low, precipitation, conditions). It does not mention potential limitations like missing location handling, but the added context is substantial.

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 four sentences, front-loaded with the core function and supported by source, output, defaults, and use cases. Every sentence contributes new information, and there is no redundancy or fluff.

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?

The description is rich for a historical data tool: it covers data source, time range, defaults, output fields, and intended use cases. However, since all 11 parameters are optional, it does not clarify what happens if no location is provided (which could cause an error or unexpected behavior), leaving a minor gap in completeness.

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

Parameters3/5

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

The input schema has 100% description coverage for all parameters, including aliases and defaults, so the baseline is 3. The description adds a high-level summary ('Pass a city or lat/lon + date range') but does not provide additional per-parameter meaning beyond what the schema already documents.

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 identifies the tool as providing historical daily weather data for any location, back to 1940, with a specific verb ('get') and resource ('historical daily weather'). It distinguishes itself from siblings like get_forecast and get_weather by emphasizing the historical aspect and referencing ERA5, making its purpose unmistakable.

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

Usage Guidelines4/5

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

The description explicitly lists use cases (e.g., 'what was the weather in X on date Y', climate baselines) and notes default behavior for missing dates. However, it does not explicitly contrast with get_forecast/get_weather or state when not to use it, so it falls short of a full 5.

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.