Skip to main content
Glama

get_weather

Read-onlyIdempotent

Retrieve current weather observations from MeteoSwiss stations by station code; use weather history for past dates.

Instructions

Current weather at a MeteoSwiss station. For past dates use get_weather_history

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>"
    },
    "name": "get_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
stationYesStation code, e.g. BER, ZUE, LUG, GVE, SMA

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / station / description
      Previous value: -"Station code (e.g. BER, ZUE, LUG, GVE, SMA)"New value: +"Station code, e.g. BER, ZUE, LUG, GVE, SMA"
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered without the description. The description adds only the 'current' framing (live observation rather than forecast) and the history pointer; it says nothing about data freshness, units, or what happens with an invalid station code.

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, zero waste, with the core purpose front-loaded before the disambiguation clause. Nothing here could be removed without losing information.

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?

For a one-parameter read-only lookup with full schema coverage and four annotations, this is nearly complete. The only meaningful omission is a hint about the returned observation fields, since there is no output schema to document them.

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% and the single parameter carries concrete station-code examples (BER, ZUE, LUG, GVE, SMA), so the schema does the work. The description adds no meaning about the parameter beyond what is already structured, which is the expected baseline here.

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 the resource and scope precisely ('Current weather at a MeteoSwiss station') and explicitly separates itself from the history sibling. The retrieval verb is implicit rather than stated, and it doesn't note that station codes come from list_weather_stations, but an agent can still tell what this tool returns.

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?

Gives a clear routing rule for the main ambiguity: 'For past dates use get_weather_history.' It does not cover the related case of discovering or validating a station code, which is what list_weather_stations and search_stations exist for, so the exclusions are incomplete but the primary guidance is explicit.

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