Skip to main content
Glama

Open Meteo Forecast

open_meteo_forecast
Read-onlyIdempotent

"What's the weather in [city]" / "weather forecast for [location]" / "will it rain tomorrow", "rain chance / probability this week" / "temperature in [place] this week" / "wind / precipitation / humidity forecast", global weather forecast up to 16 days ahead, hourly or daily, at any lat/lng. Returns temperature, precipitation, wind, humidity, cloud cover, weather codes by default; pass hourly/daily arg for custom variables. Free, keyless, no signup (Open-Meteo / ECMWF + national weather services). Pair with geocode to convert "Paris" -> lat/lng first.

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": {
      "latitude": 40.7128,
      "longitude": -74.006,
      "forecast_days": 10,
      "temperature_unit": "fahrenheit"
    },
    "name": "open_meteo_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
dailyNoComma-separated daily variables. Default sensible set.
hourlyNoComma-separated hourly variables. Default sensible set.
latitudeYes
timezoneNoIANA timezone or "auto"
longitudeYes
past_daysNo0-92 (default 0)
forecast_daysNo1-16 (default 7)
wind_speed_unitNokmh | ms | mph | kn
temperature_unitNocelsius (default) | fahrenheit

Output Schema

NameRequiredDescriptionDefault
dailyNoDaily forecast data
hourlyNoHourly forecast data
latitudeNoQuery latitude
timezoneNoIANA timezone string
elevationNoElevation of the location in meters
longitudeNoQuery longitude
daily_unitsNoUnits for daily variables
hourly_unitsNoUnits for hourly variables
generationtime_msNoAPI response generation time in milliseconds
utc_offset_secondsNoUTC offset in seconds for the requested timezone

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuinely useful context beyond them: free, keyless, no signup, forecast horizon of 16 days, and the default variable set returned (temperature, precipitation, wind, humidity, cloud cover, weather codes). It does not mention rate limits or pagination, but for a free public read API that is minor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Compact and front-loaded — user phrasings first, then capability, then return defaults, then auth and the geocode prerequisite. The slash-separated phrase list is dense and a couple of examples are near-duplicates ("temperature in [place] this week"), but no sentence is filler.

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?

An output schema exists, so the brief mention of returned variables is sufficient rather than required. Combined with units and ranges in the schema and the auth/geocode notes, an agent has everything needed to call it correctly; only the absence of any mention of error behavior or non-forecast alternatives leaves a small gap.

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 78% and the schema already documents ranges for forecast_days, past_days, and unit options. The description adds meaning the schema lacks: what the default variable set actually contains, and that hourly/daily must be passed to override it with custom variables. latitude/longitude carry no schema description, but the geocode pairing sentence compensates for that.

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?

States a specific resource and scope: "global weather forecast up to 16 days ahead, hourly or daily, at any lat/lng." The query-phrase openers ("what's the weather in [city]", "will it rain tomorrow") make the intent unmistakable, and naming Open-Meteo/ECMWF plus the geocode pairing separates it from siblings like open_meteo_marine and open_meteo_air_quality.

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?

Gives concrete triggering phrasings and an explicit prerequisite workflow: "Pair with geocode to convert 'Paris' -> lat/lng first," which is essential since lat/lng are required. It does not state exclusions (e.g. historical vs. forecast, or when to prefer the marine/air-quality siblings), so it stops short of full when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.