Skip to main content
Glama

Get Turkish APRS net schedule

get_turkish_aprs_net
Read-onlyIdempotent

Returns the schedule published on aprs.world for the Turkish APRS on-the-air net ("APRS Çevrimi"): whether it is active, title, day of week, local time and time zone, frequency, coordinator callsign, description, next session time (UTC) and the last session summary. The text fields are entered by the net coordinator.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond them: the upstream source (aprs.world) and the caveat that text fields are coordinator-entered, implying possible staleness. It does not say what is returned when the net is inactive or the upstream is unavailable, or whether missing fields can be null.

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?

Two tightly packed sentences, front-loaded with the scope and source before the field enumeration. The long field list is justified because no output schema exists, so those names are the only return-value documentation available.

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 enumeration of returned fields (active flag, title, day/time/timezone, frequency, coordinator callsign, description, next session in UTC, last session summary) does the job an output schema would. The remaining gap is failure/inactive behavior and whether coordinator-entered fields may be absent, which matters given the open-world annotation.

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 tool takes zero parameters, so the baseline is 4 and there is no parameter meaning the description could add. The description instead spends its detail on returned fields, which is the right allocation for a parameterless call.

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 ("Returns") and a precisely scoped resource (the schedule published on aprs.world for the Turkish APRS on-the-air net), then enumerates what the schedule contains. Nothing in the sibling catalog overlaps: the rest are station-level tools, so an agent can route unambiguously.

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?

The description makes the use context clear by naming the exact net and its source, so an agent knows this answers questions about this specific net. It gives no explicit when-not or prerequisite guidance, but with zero parameters and no comparable sibling there is little alternative-selection ambiguity to resolve.

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