Skip to main content
Glama
eqsl-mcp

eqsl-mcp

by qso-graph

Eqsl Inbox

eqsl_inbox
Read-onlyIdempotent

Download incoming eQSL cards that other amateur radio operators have sent you. Filter by date, QTH profile, or confirmation status to review your received contacts.

Instructions

Download incoming eQSLs (confirmations others have sent you).

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_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoOnly records added since this date (YYYY-MM-DD). Default: last 30 days.
personaYesPersona name configured in adif-mcp.
qth_nicknameNoQTH profile name (for multi-QTH callsigns).
confirmed_onlyNoOnly return records you have confirmed back.
unconfirmed_onlyNoOnly return records you have NOT confirmed.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds a clarification of what an eQSL is, but says nothing about whether downloading has side effects on server state, pagination, volume limits, or authentication needs beyond the persona parameter.

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?

A single front-loaded sentence with a parenthetical clarification and zero waste. Nothing is padded or buried.

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 100% schema coverage, an output schema, and annotations covering safety and openness, the description is nearly sufficient. The one real gap is distinguishing this tool from eqsl_download, which matters for a five-sibling eQSL tool set.

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 the meaning of since, persona, qth_nickname, confirmed_only and unconfirmed_only is fully documented in the schema. The description restates none of this and adds no semantics of its own; baseline 3 applies.

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?

States a specific verb+resource (download incoming eQSLs) and adds a helpful gloss that these are confirmations sent by others. However it does not differentiate from the sibling eqsl_download, which sounds nearly identical, so an agent cannot fully disambiguate from the description alone.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus eqsl_download, eqsl_last_upload, or eqsl_verify, and no exclusions or prerequisites. The agent must infer the difference from the name alone.

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