Skip to main content
Glama

get_weather_history

Read-onlyIdempotent

Retrieve historical weather readings for a MeteoSwiss station by station code and date range within the last 32 days, with raw, hourly, or daily resolution.

Instructions

Historical weather readings for a MeteoSwiss station. Only the last 32 days are available

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": {
      "station": "<station>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_weather_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
stationYesStation code, e.g. BER
end_dateYesYYYY-MM-DD
resolutionNoauto summarises long ranges to min/max/mean per periodauto
start_dateYesYYYY-MM-DD, within the last 32 days

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.0
    • changedInput schema / properties / end_date / description
      Previous value: -"End date YYYY-MM-DD"New value: +"YYYY-MM-DD"
    • addedInput schema / properties / resolution
      Added value: +{
      +  "default": "auto",
      +  "description": "auto summarises long ranges to min/max/mean per period",
      +  "enum": [
      +    "auto",
      +    "raw",
      +    "hourly",
      +    "daily"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / start_date / description
      Previous value: -"Start date YYYY-MM-DD"New value: +"YYYY-MM-DD, within the last 32 days"
    • changedInput schema / properties / station / description
      Previous value: -"Station code (e.g. BER)"New value: +"Station code, e.g. BER"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/openWorld, so safety is covered. The description adds one genuinely useful behavioral constraint — the 32-day availability window — but says nothing about what happens when a caller requests an out-of-range window (error vs. silent truncation) and nothing about 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 short sentences, with the resource identified first and the hard constraint front-loaded. No redundant or filler wording.

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

Completeness3/5

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

With no output schema, the description never indicates what a 'reading' contains (temperature, precipitation, wind, etc.) or the response structure, which matters for a data-fetch tool. The availability window is covered, but the payload is left entirely opaque.

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%, including the resolution enum and date formats, so the schema carries parameter meaning. The description adds no parameter-level detail beyond the schema; baseline 3 applies.

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?

States a specific verb+resource ('Historical weather readings') and the data source ('MeteoSwiss station'), which separates it from get_weather (current conditions) and get_water_history. It does not explicitly name those siblings as alternatives, so it stops short of a 5.

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?

Usage is implied by 'Historical... Only the last 32 days are available', so an agent can infer this is for recent past conditions rather than forecasts. There is no explicit statement of when to prefer get_weather or what to do for ranges older than 32 days.

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