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

io.github.qso-graph/pota-mcp

by qso-graph

Pota Park Leaderboard

pota_park_leaderboard
Read-onlyIdempotent

Get a POTA park's activator and hunter leaderboards, showing activation counts and activator/hunter QSO totals by callsign.

Instructions

Top activators and hunters of a POTA park.

Three boards: most activations, most QSOs as an activator, most QSOs as a hunter. Each row is a callsign and a count and nothing else.

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": {
      "reference": "<reference>"
    },
    "name": "pota_park_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows per board (default 10, max 25). POTA currently publishes five per board, so a higher limit changes nothing until it does.
referenceYesPark reference code (e.g., US-0062).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds genuinely new context: there are exactly three boards and each row contains only a callsign and a count, which tells the agent not to expect dates, modes, or per-QSO detail.

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 short sentences, front-loaded with the purpose, then the board breakdown, then the row shape. No filler and nothing buried.

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?

A simple read tool with an output schema, full annotation coverage, and 100% parameter documentation; the description supplies the one thing structured fields don't convey — the three-board structure and minimal row fields. Nothing an agent needs to call it correctly is missing.

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%, with both reference and limit documented in the schema (including the max 25 and the note that POTA publishes only five per board). The description adds nothing about parameters, so baseline 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 resource (POTA park leaderboard) and enumerates exactly what it returns: three boards keyed by activation count, activator QSOs, and hunter QSOs, with rows of callsign+count only. That row-shape statement cleanly separates it from raw-list siblings like pota_park_activations or pota_park_stats.

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?

Usage is implied by the content (ask for rankings of a park), but the description never states when to prefer this over pota_park_stats or pota_park_activations, nor any prerequisite such as needing a valid park reference first. Adequate but with a clear gap.

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