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": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
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. |
| 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_lookupB | 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_searchB | Find codes whose name, prefixes, area wording or attributes contain every word of text. |
| darc_dok_codes_forB | 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
Several pairs have unclear boundaries: get_version_info and darc_dok_source_info both report the served edition, and darc_dok_lookup overlaps with both darc_dok_valid_on (validity window) and darc_dok_codes_for, since lookup already returns validity windows for special DOKs. The descriptions are rich enough to mostly sort it out, but an agent must read carefully to choose between lookup, search, and codes_for.
Five tools follow a clean darc_dok_<verb/preposition> snake_case pattern (lookup, search, valid_on, codes_for, source_info). get_version_info breaks the prefix convention, a minor but noticeable deviation.
Six tools is well-scoped for a read-only reference lookup server. The only redundancy is the version/source-info pair, which could arguably be one tool.
The surface covers point lookup, free-text search, date-validity, entity-level code listing, provenance/citation, and version info, which is solid for a static reference dataset. A reverse listing of all DOKs within a district is only indirectly available via search, a minor gap.