Skip to main content
Glama

Get APRS station

get_station
Read-onlyIdempotent

Returns the latest known state of one APRS station by callsign: last heard time, last reported position (WGS84 latitude/longitude), altitude (m), speed (km/h), course (degrees), station type, symbol, comment, digipeater path, device model when identifiable, packet count and first-heard time. Answers questions such as where an amateur-radio callsign is, whether it is on the air, or what it beacons. If the callsign has no exact match, the most recently heard SSID of the same operator is returned. Read-only; data is public APRS-IS traffic.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsignYesStation callsign with optional SSID, for example TA4OHN-10. Case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: the non-exact-match fallback to the most recently heard SSID of the same operator, and that the data source is public APRS-IS traffic — both material for interpreting results correctly.

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 verb and resource, then the returned fields, then usage questions, then the fallback caveat — a sensible ordering. The dense field enumeration is long for one paragraph but each field earns its place by helping an agent match a user question to this 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 a single required, fully-described parameter and no output schema, the description compensates by enumerating the returned values and their units (WGS84, m, km/h, degrees). For a single-record lookup there is no pagination or filtering concern left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents the callsign pattern, SSID suffix, and case-insensitivity, so baseline would be 3. The description nevertheless adds semantic meaning the schema cannot express: how matching degrades when there is no exact callsign hit, which changes how an agent should interpret a returned station.

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 ("Returns the latest known state of one APRS station by callsign") and then enumerates the exact payload (last heard, position, altitude, speed, course, symbol, path, device, packet count). That field list implicitly separates it from siblings like get_station_track, get_station_weather, and get_station_raw_packets, so an agent can distinguish it without opening schemas.

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 concrete usage contexts — "where an amateur-radio callsign is, whether it is on the air, or what it beacons" — which is clear when-to-use guidance. It stops short of naming alternatives or exclusions (e.g., use get_station_track for history, get_station_weather for weather fields), so sibling routing is left to inference.

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