Skip to main content
Glama
qso-graph

io.github.qso-graph/cq-zones-mcp

by qso-graph

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_version_infoA

Get cq-zones-mcp's version and the edition of CQ's list it serves.

Returns: service_name, service_version (PyPI), and spec_version (the owner's edition).

cq_zones_source_infoC

Who owns this list, which edition is served, its terms, and the owner's files' URLs and SHA-256s.

cq_zones_lookupB

One CQ zone: its name and every entity, subdivision and boundary CQ lists for it, with ADIF codes and the citation.

cq_zones_searchB

Find codes whose name, prefixes, area wording or attributes contain every word of text.

cq_zones_codes_forB

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation4/5

Most tools have clearly distinct purposes: lookup, search, reverse entity lookup, validity check, and source metadata. get_version_info and cq_zones_source_info both provide metadata about the service/list, which could cause slight confusion, but the descriptions differentiate version details from ownership and files.

Naming Consistency4/5

Five tools use the consistent cq_zones_ prefix, making the domain grouping clear. get_version_info uses a different get_ convention for the service-level metadata, which is a minor deviation but still readable and predictable.

Tool Count5/5

Six tools is well-scoped for a reference-data MCP server. Each tool covers a useful query type without excessive overlap or redundancy.

Completeness4/5

The read-only surface covers version/source metadata, single-zone lookup, text search, entity-to-zone reverse lookup, and validity checking. A direct list-all-zones operation is absent, but search and lookup likely let agents work around this minor gap.