itu-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": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_version_infoA | Get itu-zones-mcp's version and the edition of the IARU's list it serves. Returns: service_name, service_version (PyPI), and spec_version (the owner's edition). |
| itu_zones_source_infoA | Who owns this list, which edition is served, its terms, and the owner's files' URLs and SHA-256s. |
| itu_zones_lookupA | One ITU zone: every prefix, subdivision and boundary the IARU lists for it, with ADIF codes and the citation. Zones 76-77 and 79-89 have no entry in this edition. |
| itu_zones_searchB | Find codes whose name, prefixes, area wording or attributes contain every word of text. |
| itu_zones_codes_forA | Which ITU zones cover an ADIF DXCC entity, or one of its subdivisions. Where the IARU splits an entity by a line (W7 states at 110W), each zone is returned with the IARU's boundary wording. |
| itu_zones_valid_onA | Whether an ITU zone was valid on a date. The chapter 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
The query tools (lookup, search, codes_for, valid_on) each target a distinct question and are clearly separable. The only mild overlap is between get_version_info (service/edition versioning) and itu_zones_source_info (data ownership/edition terms), which both surface metadata and could be confused at a glance.
Five of six tools use a consistent snake_case itu_zones_ prefix (lookup, search, codes_for, valid_on, source_info), giving a predictable pattern. get_version_info breaks the prefix convention, a minor deviation from an otherwise uniform scheme.
Six tools is well-scoped for a focused reference-lookup server. Each tool covers a distinct query type with no filler or redundancy.
The surface covers lookup by zone, reverse lookup by DXCC entity/subdivision, text search, validity checks, and provenance/version metadata, matching the apparent domain well. A tool to enumerate or list all zones is absent, but agents can largely work around this via search.