Skip to main content
Glama

Search APRS stations

search_stations
Read-onlyIdempotent

Searches stations by callsign prefix and, for terms of 4 or more characters, by words in the station's beacon comment (for example a locality or club name typed by the operator). Returns up to 25 matches with callsign, type, position (WGS84), comment and last-heard time (UTC); exact callsign matches come first, then most recently heard.

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": {
      "query": "<query>"
    },
    "name": "search_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesCallsign prefix or short comment word, 4–9 characters: letters, digits and . / + - only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a hard cap of 25 results, the fields returned, UTC timestamps, and the ranking rule (exact callsign matches first, then most recently heard). It does not say whether more than 25 matches can be paged to, which is the one remaining gap.

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 dense clauses, front-loaded with the search modes and followed by the return contract. Nearly every phrase carries information, though the parenthetical example about locality or club names could be trimmed with little loss.

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 correctly takes on the burden of describing the return shape — fields, count limit, ordering and time zone. Combined with annotation coverage of the safety profile and full schema coverage of the one parameter, an agent has what it needs; only the pagination question is left open.

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?

The schema already documents the single query parameter at 100% coverage including the character pattern, so the baseline is 3. The description goes beyond it by explaining what the string is interpreted as (callsign prefix vs. comment word), the 4-character threshold that switches modes, and the operator-typed locality/club examples — real semantic value not present in the schema.

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?

States a specific verb and resource ('Searches stations') plus the two matching modes: callsign prefix and, for terms of 4+ characters, words in the beacon comment. An agent can tell this is a fuzzy search rather than an exact lookup, though no sibling (e.g. get_station) is named to sharpen the distinction.

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 matching rules imply when the tool is appropriate (partial callsigns, free-text locality/club terms) and the 4-character threshold implicitly excludes very short queries from comment matching. However, there is no explicit statement of when to prefer this over get_station or find_stations_near_station, or of when-not-to-use.

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