Skip to main content
Glama
Sign In

met-mcp

by io.github.trondbjoroy
OverviewDiscussionsAdmin

Get historical weather

get_historical_weather

Daily historical observations from a weather station (Frost archive, some stations go back over 100 years). Find station ids with find_weather_stations.

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_id": "<station_id>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "get_historical_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesEnd date (exclusive), YYYY-MM-DD
fromYesStart date, YYYY-MM-DD
elementsNoFrost element ids. Defaults: daily mean temperature, precipitation sum, max wind.
station_idYesStation id from find_weather_stations, e.g. SN50540

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/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 of behavioral disclosure. It reveals the data source (Frost archive) and the depth of history (100+ years), which informs expectations about temporal coverage. However, it does not disclose output format, pagination, units, error handling, or any access limitations—gaps that are material for an agent.

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 sentence that front-loads the core action ('Daily historical observations') and immediately follows with useful context (Frost archive, 100-year span) and a practical pointer (find_weather_stations). Every word earns its place with no redundant or vague 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 and no annotations, the description is sparse. It covers the purpose and prerequisite but omits return-value details (e.g., units, format, whether data is aggregated daily) and error behavior (e.g., missing data handling). While the schema explains parameters, an agent still lacks enough information to confidently interpret the tool's response.

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?

The input schema provides 100% coverage with descriptive text for all four parameters, including defaults for 'elements' and pattern constraints for dates. The description adds no extra parameter-level meaning beyond pointing to find_weather_stations for station_id, which is already implied in the schema. The baseline of 3 is appropriate when schema covers everything.

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?

The description clearly states the core function: 'Daily historical observations from a weather station.' It specifies the data source (Frost archive) and historical depth (over 100 years), which distinguishes it from sibling tools like get_forecast and get_nowcast. The purpose is unambiguous and correctly frames the tool's scope.

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?

The description explicitly instructs to use find_weather_stations to locate station ids, providing a clear prerequisite for use. It implies historical usage via the word 'historical' but does not explicitly contrast with forecast/nowcast tools. The guidance is helpful but could be more explicit about when not to use this tool.

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

All met-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources