Skip to main content
Glama
Sign In
io.github.qso-graph/pota-mcp

io.github.qso-graph/pota-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Pota Scheduled

pota_scheduled
Read-onlyIdempotent

Retrieve upcoming scheduled POTA activations and filter them by location, activator callsign, park reference, or hours from now to plan park activation activities.

Instructions

Get upcoming scheduled POTA activations.

All filters are optional and combine with AND — omit them all and the whole schedule comes back, as before.

Input Schema

NameRequiredDescriptionDefault
locationNoFilter by location code (e.g., US-ID, CA-ON). Matches a park that spans regions, so US-MD finds a park listed as US-VA,US-MD. Empty for all.
activatorNoFilter by activator callsign (e.g., N3VEM). Empty for all.
referenceNoFilter by park reference (e.g., US-0058). Empty for all.
within_hoursNoOnly activations whose start time falls between now and this many hours from now. An activation already under way is not included — pota_spots is what reports the air now. Omit for no time limit.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.6.0
    • addedInput schema / properties / activator
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": "",
+  "description": "Filter by activator callsign (e.g., N3VEM). Empty for all."
+}
    • addedInput schema / properties / location
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": "",
+  "description": "Filter by location code (e.g., US-ID, CA-ON). Matches a park\nthat spans regions, so US-MD finds a park listed as US-VA,US-MD.\nEmpty for all."
+}
    • addedInput schema / properties / reference
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": "",
+  "description": "Filter by park reference (e.g., US-0058). Empty for all."
+}
    • addedInput schema / properties / within_hours
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only activations whose start time falls between now and\nthis many hours from now. An activation already under way is not\nincluded — pota_spots is what reports the air now. Omit for no\ntime limit."
+}
  2. First observedv0.2.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world behavior, so the bar is lower; the description still adds the non-obvious AND-combination rule and the default 'return whole schedule' behavior. The trailing 'as before' adds no information for an agent without prior context.

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 tight sentences with the core purpose front-loaded and no wasted preamble. The parenthetical 'as before' is the only baggy fragment.

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?

An output schema exists and all four parameters are fully documented, so the description needn't explain returns. It supplies the filter-combination and empty-filter default, leaving only result ordering and typical result size unstated.

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 baseline is 3; the description earns one more by documenting cross-parameter semantics (filters AND together) that the per-field schema descriptions do not express.

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 ('Get upcoming scheduled POTA activations'), which is clearly distinct from stats/leaderboard siblings. It does not explicitly distinguish itself from the closest sibling, pota_spots (reports current activations), leaving that contrast only in a parameter description.

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?

It explains the filtering model ('all optional, combine with AND, omit for everything'), which implies usage. But it never says when to prefer this over pota_spots or pota_park_activations, so routing guidance is left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools