Skip to main content
Glama
cmer81

Open-Meteo MCP Server

by cmer81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

metno_forecast

Retrieve weather forecasts for Nordic countries using high-resolution data from the Norwegian weather service. Specify location coordinates to get hourly and daily weather variables for planning and analysis.

Instructions

Get weather forecast from Norwegian weather service with high-resolution data for Nordic countries.

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 are provided, so the description carries the full burden. It only states the tool gets a forecast, but does not disclose data recency, resolution limits, or other behavioral traits essential for an agent to understand the tool's behavior.

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 is a single, well-structured sentence that immediately conveys the core purpose. No redundant information, every word earns its place.

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?

The tool has 11 parameters and no output schema, yet the description offers no information about response format, data structure, or how the high-resolution aspect manifests. For a tool with this complexity, the description is too brief to be complete.

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 description coverage is 100%, so the baseline is 3. The description does not add extra meaning beyond what's in the schema; it remains generic. No parameter details are elaborated in the description.

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?

The description clearly states it gets a weather forecast from the Norwegian service, with a specific resource and verb. It mentions 'high-resolution data for Nordic countries', which helps differentiate it from generic weather tools and other regional ones, though the differentiation is implicit.

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 explicit guidance on when to use this tool versus the many sibling tools. It implies Nordic focus but doesn't state when not to use it or name alternatives. The description lacks context for selection.

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