Skip to main content
Glama
cmer81

Open-Meteo MCP Server

by cmer81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

weather_forecast

Retrieve weather forecasts for specific coordinates, including hourly and daily data with customizable variables like temperature, precipitation, and wind conditions.

Instructions

Get weather forecast data for coordinates using Open-Meteo API. Supports hourly and daily data with various weather variables.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesLatitude in WGS84 coordinate system
longitudeYesLongitude in WGS84 coordinate system
hourlyNoHourly weather variables to retrieve
dailyNoDaily weather variables to retrieve
current_weatherNoInclude current weather conditions
temperature_unitNoTemperature unitcelsius
wind_speed_unitNoWind speed unitkmh
precipitation_unitNoPrecipitation unitmm
timezoneNoTimezone for timestamps (e.g., Europe/Paris, America/New_York)
past_daysNoInclude past days data
forecast_daysNoNumber of forecast days

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.3

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided. Description does not disclose behavioral traits such as rate limits, data source limitations, default units, or response format. It only mentions using Open-Meteo API.

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?

Two sentences, brief and to the point. Could be slightly more informative without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 11 parameters, no output schema, and no annotations, the description is lacking. It does not cover output format, error handling, usage limits, or how this tool fits among the many sibling forecast tools.

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?

Schema coverage is 100% with parameter descriptions. The description adds only a generic summary ('Supports hourly and daily data with various weather variables'), which provides minimal additional value beyond the schema.

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?

Clearly states verb (Get), resource (weather forecast data for coordinates), and mentions hourly and daily data. However, it does not differentiate from sibling forecast tools like dwd_icon_forecast or weather_archive.

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?

No guidance on when to use this tool vs alternative forecast models or the weather_archive tool. The description lacks context for choosing among siblings.

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

Deploy Server

Other Tools