Skip to main content
Glama

Get station weather reports

get_station_weather
Read-onlyIdempotent

Returns weather reports sent by an APRS weather station for the last 1–48 hours: temperature (°C), humidity (%), pressure (hPa), wind direction (degrees), wind speed and gust (m/s), rain in the last hour and 24 hours (mm). Gives the latest report in full, minimum/maximum over the window for the main values, and an evenly thinned series (at most 48 points). Stations that do not send weather return an empty result.

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": {
      "callsign": "<callsign>"
    },
    "name": "get_station_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNoHow far back to read weather reports, in hours (1–48, default 6).
callsignYesStation callsign with optional SSID, for example TA4OHN-10. Case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds substantive behavior: the return shape (latest report in full, min/max over the window, a series thinned to at most 48 points) and the edge case that weather-less stations yield an empty result. Units for every field are spelled out, which is real added value with no output schema.

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 purpose, then the metric list with units, then the return-structure summary, then the empty-result caveat. The metric enumeration is long but each unit-bearing item carries information an agent needs given there is no output schema; only minor trimming would be possible.

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 two-parameter, read-only tool with no output schema, the description covers what is returned, how the series is thinned, the time window, and the empty-result case. Nothing an agent needs in order to call it correctly appears missing, though the pagination/point-count interaction with the hours window could be spelled out slightly more.

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%, so both parameters (callsign pattern and the 1–48 hour window) are already fully documented in the schema. The description restates the window range but adds no new syntax, default, or format guidance beyond it, so the baseline score 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: 'Returns weather reports sent by an APRS weather station', and enumerates exactly which measurements come back (temperature, humidity, pressure, wind, rain). It is clearly distinguishable from siblings like get_station_telemetry or get_station_raw_packets by the weather-metric scope, though no sibling is named 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 1–48 hour window and the note that non-weather stations return an empty result imply when this tool is appropriate, but there is no explicit 'use this when…' or routing to an alternative such as get_station_telemetry for non-weather data. Usage is inferable rather than stated.

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.

Resources