Skip to main content
Glama
eqsl-mcp

eqsl-mcp

by qso-graph

Eqsl Download

eqsl_download
Read-onlyIdempotent

Download your complete eQSL inbox as raw ADIF text and save it to disk for import into your logger. Omit the since date to retrieve your full history.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "persona": "<persona>"
    },
    "name": "eqsl_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoOnly records added since this date (YYYY-MM-DD). Omit for full history.
personaYesPersona name configured in adif-mcp.
qth_nicknameNoQTH profile name (for multi-QTH callsigns).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds useful context beyond them by stating that the return value is raw .adi file content intended to be written to disk, which tells the agent how to handle the response rather than just displaying it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the purpose front-loaded, followed by the return shape and the default-scope note. No filler and no redundancy beyond a minor overlap with the schema on 'since'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't document return values, and it still usefully notes the .adi format and disk-save step. It is nearly complete for a low-complexity read tool; only the absence of sibling routing keeps it from full coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all three parameters (since, persona, qth_nickname) are already documented with formats and defaults. The description restates the 'since' omission behavior but adds nothing about persona or qth_nickname selection, so it merely duplicates structured data at the baseline level.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Download your complete eQSL inbox') and states the output format ('raw ADIF text', '.adi file content'), which is a concrete and distinguishable purpose. It doesn't explicitly contrast itself with the sibling eqsl_inbox, leaving the agent to infer the difference between a raw file download and an inbox listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'save to disk for import into your logger' hints at the download-then-import workflow, and 'Omit since to download your entire inbox history' describes parameter behavior rather than when to select this tool over eqsl_inbox. There is no explicit when-to-use versus sibling guidance or statement of exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.