adif-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 | Returns the version of the ADIF-MCP server and spec. |
| calculate_distanceB | Calculates distance (km) between Maidenhead locators. |
| calculate_headingB | Calculates heading (azimuth) between Maidenhead locators. |
| parse_adifC | Streaming parser for large ADIF files with record seeking. SECURITY NOTE: This tool reads files from the local filesystem using the provided path. Only pass paths to ADIF log files you own. |
| read_specification_resourceA | Reads an ADIF 3.1.7 specification resource (e.g., 'mode', 'fields', 'all'). An unknown or unreadable name is a tool execution error, so the model can see it failed and correct the name rather than being handed an error document that looks like a successful result. |
| list_enumerationsA | Lists the 26 enumerations: ADIF 3.1.7's 25 plus Country (derived). Each entry's |
| search_enumerationsC | Searches ADIF 3.1.7 enumerations. Optionally filter by enumeration name. |
| validate_adif_recordB | Validates an ADIF record against 3.1.7 rules including enum membership. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_system_version | Provides the current service and ADIF specification versions. |
TDQS
Scored across 8 tools
Most tools target distinct actions (parsing, validation, spec reading, geo math), and the list vs search enumeration pair is clarified by descriptions. The calculate_distance vs calculate_heading pair and read_specification_resource vs list_enumerations overlap slightly, but outputs are well differentiated.
All tools follow a consistent snake_case verb_noun pattern (get_version_info, calculate_distance, parse_adif, list_enumerations, search_enumerations, validate_adif_record). No mixed conventions.
Eight tools is well-scoped for an ADIF reference/validation server, with each tool covering a distinct capability (version, geo, parsing, spec, enumerations, validation). Nothing feels padded or missing for the stated purpose.
The read/validate/spec-reference surface is solid, covering parsing, validation, enumerations, and spec lookup. However, there is no write/export or record-modification tool, which is a noticeable but workable gap for an ADIF-focused server.