Skip to main content
Glama
Sign In
hamqth-mcp

hamqth-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Hamqth Dx Spots

hamqth_dx_spots
Read-onlyIdempotent

Retrieve live HamQTH DX cluster spots updated every ~15 seconds. Filter by band or callsign to find active stations and track specific operators.

Instructions

Live DX cluster spots from HamQTH (public, no auth required).

Spots update every ~15 seconds. Max 200 spots per request.

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

Input Schema

NameRequiredDescriptionDefault
bandNoOptional ADIF band filter (e.g., "20M", "40M").
callNoOptional callsign filter — matches spotted call or spotter (case-insensitive, e.g., "3Y0K"). Pulls max spots and filters client-side since the API does not support server-side filtering.
limitNoNumber of spots to return (default 60, max 200).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and open-world behavior, so the safety profile is covered. The description adds useful operational context beyond that: no authentication is required and the data refreshes roughly every 15 seconds, which matters for a live feed. It does not mention rate limits or error behavior, keeping it short of a 5.

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 what the tool returns, followed by freshness and volume constraints. Every sentence carries information an agent would use, with no filler.

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, so return formatting need not be explained, and annotations carry the safety profile. The description covers source, auth, refresh cadence and result ceiling, which is nearly everything needed to call it correctly; only rate-limit or failure behavior is absent.

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 band, call and limit each documented including the client-side filtering caveat for call. The description only restates the 200-spot ceiling already present in the limit parameter, so it adds little beyond the schema; baseline 3 applies.

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?

The description states a specific verb and resource ('Live DX cluster spots from HamQTH') and adds the source and auth model, so the agent knows exactly what data it returns. It does not distinguish itself from the spot-like sibling hamqth_rbn, which is the only missing differentiator.

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 supplies clear context (public, no auth, ~15s refresh) that implies when the tool is appropriate, but it never says when to prefer hamqth_rbn or another sibling, nor does it state any exclusions. Usage is inferable rather than explicit.

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