Skip to main content
Glama

List APRS Thursday participants

list_aprs_thursday_participants
Read-onlyIdempotent

Lists the stations that checked in to the weekly APRS Thursday net on a UTC date, grouped by country, with totals. The counting window is that Thursday 00:00 UTC minus 6 h to the next day 00:00 UTC plus 6 h, one station per callsign-SSID. Defaults to today (UTC). At most 25 callsigns are listed per country; counts are complete.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_aprs_thursday_participants"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoUTC date of the net, YYYY-MM-DD. Defaults to today (UTC).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds genuinely non-obvious behavior: the ±6 h counting window around the Thursday, one-station-per-callsign-SSID deduplication, and the 25-callsign-per-country listing cap with the assurance that counts remain complete. Those truncation and dedup rules are exactly the kind of caveat an agent cannot infer from annotations or schema.

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 tight sentences: purpose first, then the counting-window definition, then the default and the truncation caveat. Every clause carries information an agent needs and nothing is repeated from the schema verbatim beyond the default value.

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 one optional parameter and no output schema, the description does the return-shape work itself: grouped by country, totals included, listing capped per country. An agent can predict the response form and call the tool correctly without further information.

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% and the sole parameter's pattern and default are already documented in the schema, so the baseline of 3 applies. The description adds only the framing that the date selects the net's counting window, which is mild but real added meaning.

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 ('Lists') and a tightly scoped resource ('stations that checked in to the weekly APRS Thursday net on a UTC date'), plus the grouping shape. That specificity implicitly separates it from the sibling net tool (get_turkish_aprs_net) and the generic station lookups, but 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?

The description gives the default behavior ('Defaults to today (UTC)') and the relevant time window, which tells an agent how to call it, but there is no explicit when-to-use vs. when-not or named alternative such as the Turkish net tool. Usage is implied rather than directed.

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