Skip to main content
Glama

Meteostat

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Monthly Normals

get_monthly_normals
Read-onlyIdempotent

Monthly climate normals for a station — long-run averages of temperature, precipitation, and pressure by calendar month. Useful for "what's normal in May here" baselines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
station_idYesMeteostat station ID — from find_stations

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of monthly normal records (typically 12)
normalsYesMonthly climate normals
station_idYesMeteostat numeric station ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / station_id / description
      Previous value: -"Meteostat numeric station ID"New value: +"Meteostat station ID — from find_stations"
  2. Changed1 schema field changed
    • changedInput schema / properties / station_id / description
      Previous value: -"Meteostat station ID — from find_stations"New value: +"Meteostat numeric station ID"
  3. Changed1 schema field changed
    • changedInput schema / properties / station_id / description
      Previous value: -"Meteostat numeric station ID"New value: +"Meteostat station ID — from find_stations"
  4. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "station_id": "72494"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of monthly normal records (typically 12)",
+      "type": "integer"
+    },
+    "normals": {
+      "description": "Monthly climate normals",
+      "items": {
+        "properties": {
+          "month": {
+            "description": "Month number (1-12)",
+            "type": "integer"
+          },
+          "precip_mm": {
+            "description": "Average precipitation in millimeters",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "pressure_hpa": {
+            "description": "Average pressure in hectopascals",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "reference_end_year": {
+            "description": "End year of reference period",
+            "type": "integer"
+          },
+          "reference_start_year": {
+            "description": "Start year of reference period",
+            "type": "integer"
+          },
+          "sunshine_min": {
+            "description": "Average sunshine duration in minutes",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "tavg_c": {
+            "description": "Average temperature in Celsius",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "tmax_c": {
+            "description": "Average maximum temperature in Celsius",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "tmin_c": {
+            "description": "Average minimum temperature in Celsius",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "wind_speed_kmh": {
+            "description": "Average wind speed in km/h",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "reference_start_year",
+          "reference_end_year",
+          "month"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "station_id": {
+      "description": "Meteostat numeric station ID",
+      "type": "string"
+    }
+  },
+  "required": [
+    "station_id",
+    "count",
+    "normals"
+  ],
+  "type": "object"
+}
  5. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds value by specifying that the tool returns long-run averages by calendar month, which is behavioral context beyond the annotations.

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?

Two concise sentences that are front-loaded with the purpose and include a practical example. 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?

With an existing output schema (not shown), the description adequately covers the tool's purpose and return semantics. For a simple tool with one parameter and clear annotations, it is complete.

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 a clear description of station_id linking to find_stations. The description adds meaning by detailing the return values (temperature, precipitation, pressure), which is not in the schema.

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 it retrieves monthly climate normals for a station, listing specific variables (temperature, precipitation, pressure). It distinguishes from sibling tools like get_daily_history by specifying 'monthly' and 'long-run averages'.

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

Usage Guidelines2/5

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

The description provides a use case ('what's normal in May here' baselines) but does not explicitly state when not to use it or compare with alternatives like get_daily_history. No guidance on prerequisites beyond the schema linking to find_stations.

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

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

Resources