Skip to main content
Glama
Sign In
hamqth-mcp

hamqth-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Hamqth Bio

hamqth_bio
Read-onlyIdempotent

Fetches an amateur radio operator's biography from HamQTH using a configured persona and callsign for callsign-based profile lookup.

Instructions

Fetch an operator's biography from HamQTH.

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

Input Schema

NameRequiredDescriptionDefault
personaYesPersona name configured in adif-mcp.
callsignYesCallsign to look up.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no mention of network dependency, HamQTH credentials/rate limits, or behavior when a callsign is unknown.

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?

A single compact sentence with the resource front-loaded and no filler. It is efficient, though its brevity is part of why differentiation and context are missing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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-value explanation is not needed, and the two simple string params are covered by the schema. The gap is routing context: nothing explains how this differs from hamqth_lookup or what 'persona' configuration means in practice.

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 coverage is 100%, so both parameters ('persona' and 'callsign') are documented in the schema itself. The description only implies the callsign is the lookup key and says nothing about how 'persona' selection affects the request, so 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?

States a specific verb ('Fetch') and resource ('operator's biography from HamQTH'), clearly readable as a read of biographical data. However, it does not differentiate from the sibling hamqth_lookup, which plausibly also returns operator information for a callsign, leaving the agent to infer the boundary.

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?

No guidance on when to use this rather than hamqth_lookup or hamqth_dxcc, and no prerequisites mentioned (e.g. that a valid persona must be configured). The agent must guess which HamQTH endpoint fits its need.

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