Skip to main content
Glama
Sign In
hamqth-mcp

hamqth-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Version Info

get_version_info
Read-onlyIdempotent

Retrieve running service and upstream HamQTH API versions to confirm fleet alignment and detect version drift across MCP deployments.

Instructions

Get hamqth-mcp service version and upstream HamQTH API version.

Returns the running PyPI version of hamqth-mcp and the HamQTH.com API contract in use. Use this to confirm fleet alignment across MCP deployments — agents can compare service_version and spec_version across servers to detect drift without going outside the MCP protocol.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context: it reports the *running* PyPI version rather than the latest published one, and it exposes the API contract in use, which explains why cross-server comparison is meaningful. It stops short of saying whether the lookup is cached or whether it ever hits the network for the upstream spec.

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?

Three sentences, front-loaded with what is returned before the rationale. The trailing clause 'without going outside the MCP protocol' is slightly promotional but does encode the practical point that no external call or dashboard is needed.

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 an output schema present and no parameters, the description need not enumerate return fields, and it still names the two key ones. For a trivial introspection tool this is essentially complete; only the freshness/caching semantics of the reported versions are left unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It wisely spends no words on arguments and instead describes the returned values.

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 verb and two precise resources: the hamqth-mcp service version and the upstream HamQTH API contract version, naming the actual fields (service_version, spec_version). No sibling tool in the list deals with versioning or introspection, so an agent can rule out the hamqth_lookup/dxcc/bio family without opening a schema.

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

Usage Guidelines4/5

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

Gives an explicit use case — confirming fleet alignment and detecting version drift across deployments by comparing service_version and spec_version. It lacks an explicit 'do not use this for X' exclusion, but there is no plausible competing tool for this purpose, so the guidance is functionally complete.

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