eqsl-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EQSL_MCP_ADIF | No | Path to a local ADIF file to use as a data source when EQSL_MCP_MOCK is enabled. | |
| EQSL_MCP_MOCK | No | Set to 1 to enable mock mode for testing the inbox tool without credentials. |
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
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| eqsl_inboxB | Download incoming eQSLs (confirmations others have sent you). |
| eqsl_verifyA | Check if a specific QSO exists in eQSL (public, no auth required). |
| eqsl_ag_checkA | Check if a callsign has Authenticity Guaranteed (AG) status on eQSL. Public, no auth required. Uses a cached copy of the AG member list (refreshed every 4 hours). |
| eqsl_downloadA | Download your complete eQSL inbox as raw ADIF text. Returns the .adi file content — save to disk for import into your logger. Omit 'since' to download your entire inbox history. |
| eqsl_last_uploadB | Check when a persona last uploaded QSOs to eQSL. |
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 5 tools
Each tool has a clearly distinct purpose: checking AG status, downloading inbox data, downloading incoming confirmations, checking last upload time, and verifying specific QSOs. There is no overlap in functionality, making tool selection unambiguous for an agent.
All tool names follow a consistent 'eqsl_' prefix with descriptive suffixes (e.g., ag_check, download, inbox, last_upload, verify). This uniform snake_case pattern ensures predictability and readability across the tool set.
With 5 tools, the server is well-scoped for managing eQSL interactions, covering key operations like status checks, data downloads, and verification. Each tool serves a specific, necessary function without bloat or redundancy.
The tool set covers core eQSL functionalities such as status verification, data retrieval, and upload tracking. A minor gap exists in lacking tools for uploading QSOs or managing outgoing confirmations, but agents can still perform essential read-only operations effectively.