Skip to main content
Glama
Sign In
hamqth-mcp

hamqth-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Hamqth Lookup

hamqth_lookup
Read-onlyIdempotent

Look up an amateur radio callsign on HamQTH to retrieve operator details such as name, grid, DXCC, coordinates, and QSL preferences. Use it to resolve call signs without a subscription.

Instructions

Look up a callsign on HamQTH (free, no subscription required).

Returns name, grid, DXCC, coordinates, QSL preferences, and more. Field availability depends on what the operator has published.

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_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
personaYesPersona name configured in adif-mcp.
callsignYesCallsign to look up (e.g., OK2CQR).

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?

The annotations already establish that this is a read-only, idempotent, open-world, non-destructive lookup. The description adds useful context beyond that: no subscription is required, and field availability depends on what the operator has published. It still does not mention possible failure behavior or rate limits, but with annotations covering safety it is appropriately informative.

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 three short sentences and front-loads the main action before the return-data summary and the field-availability caveat. Every sentence contributes useful information without repetition or 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 and annotations cover the safety profile, so the description need not explain return values in detail. It does enough by naming the lookup target, summarizing returned fields, and noting that field availability varies, though it could more explicitly position this tool relative to the other HamQTH siblings.

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 the persona and callsign parameters are already documented in the input schema, including an example callsign. The description does not add parameter-level meaning beyond what the schema provides, so the baseline score of 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: 'Look up a callsign on HamQTH.' It also clarifies the service is free and lists the kind of data returned. However, it does not distinguish this general lookup from narrower sibling tools such as hamqth_bio or hamqth_dxcc, even though their names suggest possible overlap.

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 name and the phrase 'Look up a callsign on HamQTH,' and the free/no-subscription note is helpful context. But the description does not explicitly say when to choose this tool over alternatives like hamqth_bio, hamqth_dxcc, or hamqth_verify_qso.

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