Skip to main content
Glama

Get station raw packets

get_station_raw_packets
Read-onlyIdempotent

Returns the most recent raw APRS packets (TNC2 text as received from APRS-IS) sent by one callsign, newest first, with the time each was received (UTC). Packet text is written by the station and returned unmodified apart from control characters and a 512-character cap per packet. The backend keeps raw packets for about 24 hours. Stations that ask not to be archived (APRS "!x!" marker) return no packets, and any single packet carrying the marker is left out.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of packets to return (1–50, default 20).
callsignYesStation callsign with optional SSID, for example TA4OHN-10. Case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 goes well beyond that with ~24 hour retention, newest-first ordering, UTC receipt times, the 512-character per-packet cap and control-character stripping. It also discloses the APRS '!x!' privacy behavior at both station and packet level, which an agent could not otherwise predict. The only minor gap is that no result-count or empty-result guidance is given beyond the privacy case.

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?

Three sentences, front-loaded with the core return value, then transformation rules, then retention and privacy caveats in descending order of importance. No filler or restatement of the title, and each sentence carries a distinct behavioral fact.

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?

For a two-parameter read tool with no output schema, the description covers what is returned, in what form, in what order, with what truncation, and for how long data exists — everything needed to call it and interpret the result. The privacy-marker exclusion is the kind of edge case that would otherwise surprise an agent, and it is stated up front.

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%, so both the callsign pattern/SSID format and the limit bounds (1–50, default 20) are already fully documented in the schema. The description adds no parameter-level meaning beyond that, 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?

States a specific verb and resource — 'Returns the most recent raw APRS packets (TNC2 text as received from APRS-IS) sent by one callsign' — plus ordering and timestamp semantics. It is distinguishable from parsed-data siblings like get_station_track or get_station_telemetry by explicitly framing the output as unmodified raw packet text.

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?

Implied usage is clear: it is the tool for raw packet inspection within the ~24 hour backend window, and the retention limit tells an agent whether the request is even viable. However, it never explicitly says when to prefer this over a parsed sibling such as get_station_track, nor does it state what to do if the window has passed — leaving the routing decision 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