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": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
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_adifB | 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_resourceB | Reads an ADIF 3.1.7 specification resource (e.g., 'mode', 'fields', 'all'). An unknown name returns an error listing the available names. |
| 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 have clearly distinct purposes: version info, distance/heading calculations, parsing, validation, spec reading, and enumeration listing/searching. The only mild overlap is between list_enumerations and search_enumerations, and read_specification_resource could partially duplicate enumeration data, but the descriptions clarify the boundaries.
All tool names use snake_case and follow a verb_noun pattern (get_version_info, calculate_distance, parse_adif, list_enumerations, validate_adif_record). The convention is consistent across the entire set.
Eight tools is well-scoped for an ADIF support server covering reference lookup, validation, parsing, and Maidenhead calculations. No tool feels redundant, and the set does not appear artificially inflated or thin.
The surface covers reading, parsing, validating, spec/enumeration lookup, and calculations, but lacks any tool to create, write, or export ADIF records. This is a notable gap if the server is meant to support full ADIF lifecycle workflows.