darc-dok-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 darc-dok-mcp's version and the edition of DARC's list it serves. Returns: service_name, service_version (PyPI), and spec_version (the owner's edition). |
| darc_dok_source_infoB | Who owns this list, which edition is served, its terms, and the owner's files' URLs and SHA-256s. |
| darc_dok_lookupC | One DOK or special DOK: the district and local club (DOKs), or the purpose, callsign, validity window and sponsoring club (special DOKs), with the citation. |
| darc_dok_searchA | Find codes whose name, prefixes, area wording or attributes contain every word of text. |
| darc_dok_codes_forA | DOK lists don't map to ADIF subdivisions: this answers for entity 230 (Germany) with nothing per subdivision. Use darc_dok_search for a district or town. |
| darc_dok_valid_onA | Whether a DOK or special DOK was valid on a date: a special DOK counts only inside the window DARC published for it. A DOK merged into another (e.g. A49, merged into A12 in 2001) shows replaced_by. |
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
Each tool serves a distinct role, but get_version_info and darc_dok_source_info both return service/list metadata, and darc_dok_lookup overlaps with darc_dok_valid_on since both take a DOK and could expose validity info. Descriptions do help clarify the boundaries.
Four tools share a clean darc_dok_ prefix, but get_version_info breaks the pattern entirely, and within the prefix naming mixes verb-style (lookup, search) with noun-style (source_info, codes_for). Still readable, though conventions are not uniform.
Six tools is well-scoped for a read-only reference dataset server: version, provenance, single lookup, search, entity mapping and date validity each earn their place without redundancy.
The surface covers provenance, discovery via search, single-code lookup, entity scoping and date-based validity—the core read-only lifecycle for reference data. A bulk/enumerate-all tool would round it out, but search largely compensates.