Open-Meteo MCP Server

Weather Archive (Historical)

weather_archive

Read-onlyIdempotent

Retrieve historical weather data from ERA5 reanalysis (1940-present) for specific coordinates and date range to analyze past climate conditions.

Instructions

Get historical weather data from ERA5 reanalysis (1940-present) for specific coordinates and date range.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tilt`	No	Solar panel tilt in degrees (0 = flat, 90 = vertical); with `azimuth`, sets global_tilted_irradiance.
`daily`	No
`hourly`	No
`models`	No	Omit to use the default model.
`azimuth`	No	Solar panel azimuth in degrees (0 = south, -90 = east, 90 = west, ±180 = north); used with `tilt`.
`end_date`	Yes	Date in YYYY-MM-DD format.
`latitude`	Yes
`timezone`	No	IANA time zone (e.g. "Europe/Paris"), or "auto" for the location's own. Default GMT.
`elevation`	No	Elevation in metres to adjust the values to; defaults to the terrain height at the point.
`longitude`	Yes
`start_date`	Yes	Date in YYYY-MM-DD format.
`timeformat`	No		iso8601
`cell_selection`	No	Grid cell to use near a coastline: prefer "land", prefer "sea", or the "nearest" cell.
`wind_speed_unit`	No		kmh
`temperature_unit`	No		celsius
`precipitation_unit`	No		mm

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedv2.5.0Sep 28, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / azimuth

Added value: +{
+  "description": "Solar panel azimuth in degrees (0 = south, -90 = east, 90 = west, ±180 = north); used with `tilt`.",
+  "maximum": 180,
+  "minimum": -180,
+  "type": "number"
+}

addedInput schema / properties / cell_selection

Added value: +{
+  "description": "Grid cell to use near a coastline: prefer \"land\", prefer \"sea\", or the \"nearest\" cell.",
+  "enum": [
+    "land",
+    "sea",
+    "nearest"
+  ],
+  "type": "string"
+}

removedInput schema / properties / daily / description

Removed value: -"Daily weather variables to retrieve"

changedInput schema / properties / daily / items / enum

Previous value: -[
-  "temperature_2m_max",
-  "temperature_2m_min",
-  "precipitation_sum",
-  "wind_speed_10m_max",
-  "shortwave_radiation_sum"
-]New value: +[
+  "weather_code",
+  "temperature_2m_max",
+  "temperature_2m_min",
+  "temperature_2m_mean",
+  "apparent_temperature_max",
+  "apparent_temperature_min",
+  "apparent_temperature_mean",
+  "sunrise",
+  "sunset",
+  "daylight_duration",
+  "sunshine_duration",
+  "precipitation_sum",
+  "rain_sum",
+  "snowfall_sum",
+  "precipitation_hours",
+  "wind_speed_10m_max",
+  "wind_gusts_10m_max",
+  "wind_direction_10m_dominant",
+  "shortwave_radiation_sum",
+  "et0_fao_evapotranspiration",
+  "cloud_cover_mean",
+  "dew_point_2m_mean",
+  "dew_point_2m_max",
+  "dew_point_2m_min",
+  "relative_humidity_2m_mean",
+  "relative_humidity_2m_max",
+  "relative_humidity_2m_min",
+  "pressure_msl_mean",
+  "wind_speed_10m_mean",
+  "wet_bulb_temperature_2m_mean",
+  "vapour_pressure_deficit_max",
+  "soil_moisture_0_to_7cm_mean",
+  "soil_moisture_7_to_28cm_mean",
+  "soil_moisture_28_to_100cm_mean",
+  "soil_moisture_0_to_100cm_mean",
+  "soil_temperature_0_to_7cm_mean",
+  "soil_temperature_7_to_28cm_mean",
+  "soil_temperature_28_to_100cm_mean"
+]

addedInput schema / properties / elevation

Added value: +{
+  "description": "Elevation in metres to adjust the values to; defaults to the terrain height at the point.",
+  "type": "number"
+}

changedInput schema / properties / end_date / description

Previous value: -"End date in YYYY-MM-DD format"New value: +"Date in YYYY-MM-DD format."

removedInput schema / properties / hourly / description

Removed value: -"Hourly weather variables to retrieve"

changedInput schema / properties / hourly / items / enum

Previous value: -[
-  "temperature_2m",
-  "relative_humidity_2m",
-  "precipitation",
-  "pressure_msl",
-  "wind_speed_10m",
-  "wind_direction_10m",
-  "shortwave_radiation"
-]New value: +[
+  "temperature_2m",
+  "relative_humidity_2m",
+  "dew_point_2m",
+  "apparent_temperature",
+  "precipitation",
+  "rain",
+  "snowfall",
+  "snow_depth",
+  "weather_code",
+  "pressure_msl",
+  "surface_pressure",
+  "cloud_cover",
+  "cloud_cover_low",
+  "cloud_cover_mid",
+  "cloud_cover_high",
+  "et0_fao_evapotranspiration",
+  "vapour_pressure_deficit",
+  "wind_speed_10m",
+  "wind_speed_100m",
+  "wind_direction_10m",
+  "wind_direction_100m",
+  "wind_gusts_10m",
+  "soil_temperature_0_to_7cm",
+  "soil_temperature_7_to_28cm",
+  "soil_temperature_28_to_100cm",
+  "soil_temperature_100_to_255cm",
+  "soil_moisture_0_to_7cm",
+  "soil_moisture_7_to_28cm",
+  "soil_moisture_28_to_100cm",
+  "soil_moisture_100_to_255cm",
+  "shortwave_radiation",
+  "direct_radiation",
+  "diffuse_radiation",
+  "direct_normal_irradiance",
+  "terrestrial_radiation",
+  "shortwave_radiation_instant",
+  "direct_radiation_instant",
+  "diffuse_radiation_instant",
+  "direct_normal_irradiance_instant",
+  "terrestrial_radiation_instant",
+  "sunshine_duration",
+  "is_day",
+  "boundary_layer_height",
+  "wet_bulb_temperature_2m",
+  "total_column_integrated_water_vapour",
+  "growing_degree_days_base_0_limit_50",
+  "leaf_wetness_probability",
+  "soil_moisture_0_to_100cm",
+  "soil_temperature_0_to_100cm",
+  "soil_moisture_index_0_to_7cm",
+  "soil_moisture_index_7_to_28cm",
+  "soil_moisture_index_28_to_100cm",
+  "soil_moisture_index_0_to_100cm",
+  "global_tilted_irradiance",
+  "global_tilted_irradiance_instant"
+]

removedInput schema / properties / latitude / description
```
Removed value: -"Latitude in WGS84 coordinate system"
```
removedInput schema / properties / longitude / description
```
Removed value: -"Longitude in WGS84 coordinate system"
```

addedInput schema / properties / models

Added value: +{
+  "description": "Omit to use the default model.",
+  "enum": [
+    "best_match",
+    "era5_seamless",
+    "era5",
+    "era5_land",
+    "ecmwf_ifs",
+    "cerra",
+    "era5_ensemble",
+    "ecmwf_ifs_analysis_long_window"
+  ],
+  "type": "string"
+}

addedInput schema / properties / precipitation_unit

Added value: +{
+  "default": "mm",
+  "enum": [
+    "mm",
+    "inch"
+  ],
+  "type": "string"
+}

changedInput schema / properties / start_date / description

Previous value: -"Start date in YYYY-MM-DD format"New value: +"Date in YYYY-MM-DD format."

addedInput schema / properties / tilt

Added value: +{
+  "description": "Solar panel tilt in degrees (0 = flat, 90 = vertical); with `azimuth`, sets global_tilted_irradiance.",
+  "maximum": 90,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / timeformat

Added value: +{
+  "default": "iso8601",
+  "enum": [
+    "iso8601",
+    "unixtime"
+  ],
+  "type": "string"
+}

changedInput schema / properties / timezone / description

Previous value: -"Timezone for timestamps"New value: +"IANA time zone (e.g. \"Europe/Paris\"), or \"auto\" for the location's own. Default GMT."

addedInput schema / properties / wind_speed_unit

Added value: +{
+  "default": "kmh",
+  "enum": [
+    "kmh",
+    "ms",
+    "mph",
+    "kn"
+  ],
+  "type": "string"
+}

First observedv1.1.3Jan 31, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds the ERA5 source and temporal coverage, but says nothing about data volume, rate limits, or response size for what is a potentially huge historical pull.

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?

A single efficient sentence that front-loads the verb, source, and scope. Nothing is wasted.

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?

For a 16-parameter historical API with no output schema, the description is thin: it omits any hint about the daily/hourly variable selection, unit controls, or the large payloads such queries return. It is adequate to identify the tool but insufficient to call it well without reading the schema.

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

Parameters2/5

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

With 16 parameters and only 50% schema description coverage, several params (latitude, longitude, timeformat, temperature_unit) have no textual explanation anywhere. The description provides zero parameter guidance, so it fails to compensate for the coverage gap it should have filled.

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 (Get), resource (historical weather data), data source (ERA5 reanalysis), range (1940-present), and required inputs (coordinates and date range). This clearly separates it from forecast siblings, but it never names an alternative, so differentiation is left to inference rather than explicit.

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 '1940-present' and 'historical' framing implies this is the past-data tool versus the many *_forecast siblings, but there is no explicit when-to-use, when-not-to-use, or named alternative. Usage is implied rather than guided.

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

Deploy Server

Weather Archive (Historical)

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools