Skip to main content
Glama

Get station reception range

get_station_reception
Read-onlyIdempotent

Summarises, for the last 24 hours, which APRS-IS gateways (iGates) with a known position received one station: the number of distinct iGates, the farthest iGate and its distance (km), and the same for the most recent transmission. Distances are great-circle kilometres between the station's position at transmit time and the iGate. For stations that ask not to be archived (APRS "!x!" marker) only the iGate count is returned: the distances come from the station's past positions.

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

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

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 and open-world, so the safety profile is covered. The description adds genuinely new behavior: the fixed 24-hour window, great-circle kilometre distances measured from the station's position at transmit time, and a real edge case — for stations using the APRS '!x!' no-archive marker only the iGate count is returned, with distances derived from past positions.

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 time window and resource, and no filler. The middle clause ('and the same for the most recent transmission') is slightly compressed and requires a re-read, but overall it earns its length given the number of returned fields it must describe without an output schema.

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 carries the return-value burden and does so by naming each metric returned plus the distance methodology. It is nearly complete for a single-parameter read tool; it omits only what happens for an unknown callsign or a station with no gateway hits in the window.

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 callsign parameter already carries format, SSID and case-insensitivity guidance. The description adds no parameter-level meaning beyond what the schema provides, so the baseline 3 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?

The description opens with a specific verb and resource: 'Summarises, for the last 24 hours, which APRS-IS gateways (iGates)... received one station', and enumerates the returned metrics (distinct iGate count, farthest iGate and km distance, and the same for the most recent transmission). That scope is specific enough to separate it from siblings like get_station_raw_packets or get_station_track, 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?

Usage is only implied: an agent can infer this is for reception-coverage/reach analysis rather than raw packet retrieval, but the description never states when to prefer it over alternatives such as get_station or get_station_raw_packets, nor any prerequisites or exclusions.

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