Skip to main content
Glama

Get station position history

get_station_track
Read-onlyIdempotent

Returns the recorded position history of one APRS station for the last 1–48 hours, oldest first: time (UTC), latitude/longitude (WGS84), altitude (m), speed (km/h) and course (degrees). Long histories are thinned evenly to at most the requested number of points, always keeping the first and the last. If nothing was recorded in the window, the most recent older points still held are returned and marked as older. Stations that ask not to be archived (APRS "!x!" marker) return no history.

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

Input Schema

NameRequiredDescriptionDefault
hoursNoHow far back to read the history, in hours (1–48, default 6).
callsignYesStation callsign with optional SSID, for example TA4OHN-10. Case-insensitive.
max_pointsNoMaximum number of track points to return (1–200, default 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: results are oldest first, long histories are evenly thinned while preserving first and last points, fallback older points are returned and marked when the window is empty, and APRS !x! stations return no history. These details materially help an agent understand output shape, ordering, and privacy-related edge cases.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose, then adds return fields, thinning behavior, fallback behavior, and the archival exception in a compact sequence. Every sentence carries useful information and there is no obvious repetition.

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?

Although there is no output schema, the description names the returned fields, their units, ordering, thinning behavior, and fallback behavior. For a read-only history retrieval tool with three fully documented parameters, this is complete enough for correct invocation and interpretation.

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%, so the schema already defines the three parameters. The description still adds useful meaning, especially for max_points by explaining that thinning is even and always keeps the first and last point, and for hours by framing it as the history window.

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-resource pair: it returns the recorded position history of one APRS station. It also specifies the time window and the exact fields returned, which clearly distinguishes it from general station lookup or raw-packet tools.

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 description makes the tool's intended context clear: retrieving historical position points for a callsign over 1–48 hours. However, it does not explicitly say when to use this instead of sibling tools such as get_station or get_station_reception, nor does it state exclusions beyond the unarchived-station case.

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