Skip to main content
Glama
eqsl-mcp

eqsl-mcp

by qso-graph

Eqsl Verify

eqsl_verify
Read-onlyIdempotent

Verify whether a specific QSO exists in eQSL using sender and receiver callsigns, band, date, and optional mode—no authentication required.

Instructions

Check if a specific QSO exists in eQSL (public, no auth required).

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": {
      "from_call": "<from_call>",
      "to_call": "<to_call>",
      "band": "<band>",
      "qso_date": "<qso_date>"
    },
    "name": "eqsl_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandYesBand (e.g., '20m').
modeNoMode (exact match — use 'USB' not 'SSB', 'PSK31' not 'PSK').
to_callYesReceiver's callsign.
qso_dateYesQSO date in YYYY-MM-DD format.
from_callYesSender's callsign.

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?

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the lookup is public and requires no authentication, which matters for how the agent sequences the call. It does not mention rate limits or how partial/mismatched data is treated, keeping it short of a 5.

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 sentence that front-loads the action and scope, then appends the auth condition. There is no filler and nothing redundant with structured fields.

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?

The tool is a simple read-only existence lookup, and its rich annotations plus a 100%-covered schema and an output schema mean the description needn't explain return values or parameters. The only minor gap is that it doesn't say the result is an exact-match existence determination, but that is largely captured elsewhere.

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 every parameter (from_call, to_call, band, qso_date, mode) is already documented, including the exact-match caveat for mode. The description adds only the implicit notion that these fields identify 'a specific QSO.' With the schema doing the heavy lifting, the 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?

The description states a specific verb and resource: check whether a specific QSO exists in eQSL. That existence-check framing clearly separates it from siblings like eqsl_inbox, eqsl_download, and eqsl_last_upload, which retrieve data. It does not name a sibling explicitly, but the scope is unambiguous.

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?

The phrase 'check if a specific QSO exists' implies the use case — confirming a single logged contact — but there is no explicit when-to-use or when-not guidance. Nothing tells the agent how this differs from eqsl_ag_check or when to prefer eqsl_download instead. Usage is inferable but not directed.

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