Meteostat

Get Daily History

get_daily_history

Read-onlyIdempotent

Daily historical weather for a Meteostat station between two dates. Returns date-keyed temperature (avg/min/max), precipitation, snow, wind, pressure, sun hours. Get a station_id from find_stations.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "end_date": "2023-12-31",
      "start_date": "2023-01-01",
      "station_id": "72494"
    },
    "name": "get_daily_history"
  }
}

Input Schema

Name	Required	Description
`end_date`	Yes	YYYY-MM-DD inclusive
`start_date`	Yes	YYYY-MM-DD inclusive
`station_id`	Yes	Meteostat station ID (e.g., "72494") — from find_stations

Output Schema

Name	Required	Description
`days`	Yes	Daily weather observations
`count`	Yes	Number of daily records returned
`end_date`	Yes	End date in YYYY-MM-DD format
`start_date`	Yes	Start date in YYYY-MM-DD format
`station_id`	Yes	Meteostat numeric station ID

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 12, 2026

changedInput schema / properties / station_id / description

Previous value: -"Meteostat numeric station ID (e.g., \"72494\")"New value: +"Meteostat station ID (e.g., \"72494\") — from find_stations"

Changed1 schema field changedJun 12, 2026

changedInput schema / properties / station_id / description

Previous value: -"Meteostat station ID (e.g., \"72494\") — from find_stations"New value: +"Meteostat numeric station ID (e.g., \"72494\")"

Changed1 schema field changedJun 12, 2026

changedInput schema / properties / station_id / description

Previous value: -"Meteostat numeric station ID (e.g., \"72494\")"New value: +"Meteostat station ID (e.g., \"72494\") — from find_stations"

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "end_date": "2023-12-31",
+    "start_date": "2023-01-01",
+    "station_id": "72494"
+  },
+  {
+    "end_date": "2024-02-15",
+    "start_date": "2024-01-15",
+    "station_id": "10382"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of daily records returned",
+      "type": "integer"
+    },
+    "days": {
+      "description": "Daily weather observations",
+      "items": {
+        "properties": {
+          "date": {
+            "description": "Date in YYYY-MM-DD format",
+            "type": "string"
+          },
+          "precip_mm": {
+            "description": "Precipitation in millimeters",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "pressure_hpa": {
+            "description": "Atmospheric pressure in hectopascals",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "snow_mm": {
+            "description": "Snow depth in millimeters",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "sunshine_min": {
+            "description": "Sunshine duration in minutes",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "tavg_c": {
+            "description": "Average temperature in Celsius",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "tmax_c": {
+            "description": "Maximum temperature in Celsius",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "tmin_c": {
+            "description": "Minimum temperature in Celsius",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "wind_dir_deg": {
+            "description": "Wind direction in degrees",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "wind_peak_kmh": {
+            "description": "Peak wind gust in km/h",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "wind_speed_kmh": {
+            "description": "Average wind speed in km/h",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "date"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "end_date": {
+      "description": "End date in YYYY-MM-DD format",
+      "type": "string"
+    },
+    "start_date": {
+      "description": "Start date in YYYY-MM-DD format",
+      "type": "string"
+    },
+    "station_id": {
+      "description": "Meteostat numeric station ID",
+      "type": "string"
+    }
+  },
+  "required": [
+    "station_id",
+    "start_date",
+    "end_date",
+    "count",
+    "days"
+  ],
+  "type": "object"
+}

First observedMay 12, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds the return format (date-keyed fields) but does not disclose additional behavioral traits such as authentication requirements, rate limits, or data latency beyond what annotations cover.

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 consists of two concise sentences, each adding essential information. No fluff or redundancy, making it easy for an AI agent to quickly grasp the tool's purpose and usage.

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?

For a tool with 3 parameters and an output schema, the description covers purpose, return fields, prerequisite (station_id from find_stations), and date range. It is complete enough, though it could mention any limitations on date ranges or data availability.

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 descriptions for all parameters. The description adds value by explaining the station_id source ('Get a station_id from find_stations') and implying the date format (YYYY-MM-DD inclusive), which goes beyond the schema alone.

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 'Daily historical weather for a Meteostat station between two dates' with specific verb, resource, and scope. It lists the returned fields and references the sibling tool find_stations for obtaining station IDs, effectively distinguishing from other weather tools.

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 provides clear context: it's for daily historical weather requiring a station_id, start_date, and end_date. It directs users to get the station_id from find_stations. However, it does not explicitly exclude using this tool for other purposes or mention alternative tools like get_monthly_normals.

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

All Meteostat 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.

Get Daily History

Example tool call

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources