Skip to main content
Glama

Get station telemetry

get_station_telemetry
Read-onlyIdempotent

Returns APRS telemetry of one station for the last 1–48 hours: up to five analog channels (already converted with the station's own calibration equations) and 8 digital bits per sample, with channel names, units and bit labels when the station published them. Evenly thinned to at most 48 samples. Stations without published calibration 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_telemetry"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds genuine value beyond that by disclosing output shape (up to five analog channels, 8 digital bits per sample, unit and bit labels) and the fact that results are evenly thinned to at most 48 samples. The empty-result behavior for stations lacking calibration is also disclosed. It stops short of describing ordering, error behavior, or what the sample timestamps look like.

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?

Two sentences, front-loaded with the return payload and with zero filler. The first sentence is long and clause-heavy (parenthetical calibration note, label lists), but each clause carries real information an agent would otherwise have to discover by calling the tool.

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

Completeness5/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 carries the return-shape burden and does so adequately for a two-parameter read tool: it explains what comes back, how it is sampled, and when it is empty. Nothing essential to correct invocation appears to be missing.

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 schema already carries the callsign pattern, example, case-insensitivity, and the 1–48 hour bounds and default. The description repeats 'last 1–48 hours' but adds no new meaning about either parameter, so the baseline of 3 applies.

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 states a specific verb and resource ('Returns APRS telemetry of one station') and pins the scope to the last 1–48 hours. The content it promises – analog channels with calibration applied, digital bits, channel names/units/bit labels – clearly separates it from sibling tools such as get_station_weather or get_station_raw_packets.

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 only implied: an agent can infer this is the tool for calibrated, aggregated telemetry, but no sibling is named and no when-not condition is stated. The one real boundary – stations without published calibration return an empty result – is useful, though it reads as an edge case rather than routing guidance.

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