Skip to main content
Glama

Find stations near a station

find_stations_near_station
Read-onlyIdempotent

Finds APRS stations heard recently within a radius (10–200 km) of the last reported position of another station given by callsign. Returns each station with callsign, type, distance (km), position (WGS84), last-heard time (UTC), speed (km/h) and comment, nearest first, excluding the centre station itself. Only stations heard within the last 30 minutes (infrastructure such as digipeaters, iGates, weather stations and objects: 24 hours) are included. The centre station must have a known position.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of stations to return (1–50, default 25).
callsignYesStation callsign with optional SSID, for example TA4OHN-10. Case-insensitive.
radius_kmNoSearch radius around the station in kilometres (10–200, default 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare read-only/idempotent/open-world; the description adds substantive behavior beyond that: a 30-minute default recency cut-off extended to 24 hours for infrastructure types, nearest-first ordering, exclusion of the centre station, and the hard precondition of a known centre position. That is exactly the operational context the annotations cannot convey.

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?

The core action and scope are front-loaded in the first clause, and the return fields are enumerated compactly. It is dense rather than bloated, though the long field list and the parenthetical recency exception slow the read slightly.

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 correctly carries the burden of describing return values (callsign, type, distance, position, last-heard, speed, comment) and their ordering. Combined with the recency rules and the known-position precondition, an agent has everything needed to call it correctly and interpret the result.

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 coverage is 100%, so the schema already documents callsign format, radius bounds and limit. The description clarifies that the radius is measured from the centre station's last reported position, which adds a little meaning, but it adds nothing about the limit parameter and repeats the 10–200 km range already in the schema.

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 gives a specific verb and resource (finds APRS stations within a radius of another station's position) plus the key discriminator: the centre is given by callsign rather than a coordinate or free-text query. The breadth of stated scope (nearest-first ordering, exclusion of the centre station) makes it distinguishable from a generic station search without opening either 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?

It states the preconditions that decide whether the tool can be used at all: the centre station must have a known position, and results are bounded by recency windows. It does not, however, name an alternative sibling (e.g. a broader station search) or say when this is the wrong choice, so it falls short of explicit when-not 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