Skip to main content
Glama

Austria: live weather stations (GeoSphere TAWES)

get_weather_at
Read-only

Free. Current 10-minute observations of 12 selected GeoSphere Austria TAWES stations (Wien, Salzburg, Innsbruck, Graz, Linz, Klagenfurt, Bregenz, Eisenstadt, St. Pölten and the mountain stations Sonnblick, Galzig, Patscherkofel): temperature, precipitation, wind speed, direction and gust, pressure, humidity, sunshine, snow depth. Values are passed through unchanged; an empty reading is null and a station without a reading is live=false. Austria only; not a forecast or warning. Source: Datenquelle: GeoSphere Austria - https://data.hub.geosphere.at (CC BY 4.0), rewritten into one format by Orb Studio; not endorsed by GeoSphere Austria.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_weather_at"
  }
}

Input Schema

NameRequiredDescriptionDefault
stationNoStation id, name or state filter, e.g. 11035, Wien, Tirol

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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety profile is covered. The description still adds real value beyond them: pass-through values, null for empty readings, live=false for a station without a reading, no cost, and a CC BY 4.0 attribution obligation. It omits return units and behavior when no station filter is supplied, which are the remaining behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core fact (free, current 10-minute observations) and then details variables, semantics, scope, and attribution. The long station parenthetical and licensing sentence are dense but each carries information an agent or end user needs; nothing is purely decorative.

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?

With no output schema, the description takes on return-value explanation and does it well (null readings, live flag, listed variables). Missing pieces are measurement units and the no-filter default result set, which matter for a tool that returns numeric observations.

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 already documents 'Station id, name or state filter' with examples. The description adds a useful constraint by naming the fixed set of 12 stations, but it does not clarify default behavior when the filter is omitted or how state filters map onto the 12 stations.

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?

States a specific verb and resource ('Current 10-minute observations of 12 selected GeoSphere Austria TAWES stations') and enumerates both the stations and the measured variables. It also rules out adjacent categories ('not a forecast or warning'), so an agent can separate it from warning/forecast-style siblings without opening the schema.

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 clear usage context: 'Free', 'Current 10-minute observations', 'Austria only; not a forecast or warning' — the geographic and temporal scope exclusions are explicit. It stops short of naming a specific alternative tool for forecasts or warnings, so routing is implied rather than directed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.