Skip to main content
Glama

get_historical_weather

Read-onlyIdempotent

Retrieve daily historical weather for a location and date range from the Open-Meteo archive, including highs, lows, precipitation, snowfall, and sky conditions (up to 366 days per call).

Instructions

Historical daily weather from the Open-Meteo archive (about 1950 to roughly five days ago): highs/lows, precipitation, snowfall and sky conditions. Ranges are capped at 366 days per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_historical_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYesEnd date (inclusive), ISO format YYYY-MM-DD.
latitudeYesLatitude in decimal degrees (-90 to 90).
longitudeYesLongitude in decimal degrees (-180 to 180).
start_dateYesStart date, ISO format YYYY-MM-DD.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description's genuine added value is the upstream data-availability window (~1950 to ~5 days ago) and the 366-day-per-call range cap, which are real behavioral constraints. It stops short of describing timezone, units, or response shape.

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 sentences, both front-loaded and load-bearing: the first establishes scope and returned variables, the second states the hard call limit. No filler or restatement of the tool name.

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 return-value documentation is unnecessary, and all four required parameters are fully described in the schema. The description covers data source, temporal window, returned variables, and the per-call range limit. Residual gaps (units, timezone handling, behavior at the archive boundary) are minor for a read-only retrieval tool.

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%, so the baseline is 3, and the description earns a bump by adding a constraint the schema does not express: the start_date/end_date pair is capped at 366 days per call, which directly governs how the date parameters must be set. It does not add unit or timezone semantics for latitude/longitude, but those are fully documented in 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?

The description names a specific verb+resource combination ('Historical daily weather') and adds the concrete source, the Open-Meteo archive, plus the measured variables (highs/lows, precipitation, snowfall, sky conditions). It is distinguishable from forecast-flavored siblings by the 'archive' and 'historical' framing, though it never names an alternative tool explicitly.

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

Usage Guidelines3/5

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

The window 'about 1950 to roughly five days ago' implicitly tells an agent this tool is for past dates rather than forecasts, and the 366-day cap signals that long ranges must be split. There is no explicit when-not or named-alternative guidance (e.g. pointing to get_daily_forecast for future dates), so usage must be inferred.

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