io.github.qso-graph/cq-zones-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_version_infoA | Get cq-zones-mcp's version and the edition of CQ's list it serves. |
| cq_zones_source_infoA | Who owns this list, which edition is served, its terms, and the owner's files' URLs and SHA-256s. |
| cq_zones_lookupA | One CQ zone: its name and every entity, subdivision and boundary CQ lists for it, with ADIF codes and the citation. |
| cq_zones_searchA | Find codes whose name, prefixes, area wording or attributes contain every word of text. |
| cq_zones_codes_forA | Which CQ zones cover an ADIF DXCC entity, or one of its subdivisions. Where CQ splits an entity (VE2 Quebec at the 50th parallel), each zone is returned with CQ's boundary wording. |
| cq_zones_valid_onA | Whether a CQ zone was valid on a date. CQ's list gives no validity window, so every zone it lists is valid; the tool exists so every owner-list server answers the same questions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Lookup, search, codes_for, and valid_on are clearly distinct operations targeting different queries. The only mild overlap is between get_version_info and cq_zones_source_info, since both return server/list metadata, though their descriptions distinguish version from ownership/terms.
Five of six tools use a consistent cq_zones_ prefix with a verb/noun tail (lookup, search, codes_for, valid_on, source_info). get_version_info breaks the pattern by using a bare get_ verb and no cq_zones_ prefix, a minor but visible deviation.
Six tools is well-scoped for a focused reference-data server. Each tool serves a distinct query need without excess, comfortably within the ideal 3-15 range.
The domain is a static CQ zone reference list, so mutation tools are unnecessary. Lookup by zone, search by text, reverse lookup by entity/subdivision, date validity, and source/version metadata cover the read surface fully with no dead ends.