Skip to main content
Glama
Sign In
hamqth-mcp

hamqth-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Hamqth Activity

hamqth_activity
Read-onlyIdempotent

Retrieve recent DX cluster, Reverse Beacon Network, and logbook activity for a callsign to monitor and verify amateur radio activity.

Instructions

Get recent DX cluster, RBN, and logbook activity for a callsign.

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": {
      "persona": "<persona>",
      "callsign": "<callsign>"
    },
    "name": "hamqth_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
personaYesPersona name configured in adif-mcp.
callsignYesCallsign to check.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the safety profile is covered. The description adds useful context by identifying the three activity sources and recency, but "recent" is vague and no time window or aggregation behavior is described.

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?

The description is a single front-loaded sentence with no wasted words. It states the tool's action, sources, and scope efficiently.

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 a complete input schema, an output schema, and rich annotations, the description is largely sufficient for calling the tool. A clearer definition of "recent" and a brief distinction from the source-specific sibling tools would make it fully complete.

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%, so both parameters are documented in the input schema. The description references the callsign parameter but adds no meaning beyond the schema, which is acceptable given full coverage.

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 uses a specific verb ("Get") and resource ("recent DX cluster, RBN, and logbook activity") scoped to a callsign. It names the data sources clearly, but does not explicitly distinguish the tool from overlapping siblings such as hamqth_dx_spots or hamqth_rbn.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It broadly implies when the tool is useful by specifying recent activity for a callsign, but gives no explicit guidance on when to use it instead of the more specific DX spot or RBN sibling tools. No exclusions or alternatives are mentioned.

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