Skip to main content
Glama
lotw-mcp

lotw-mcp

by qso-graph

Lotw Qsos

lotw_qsos
Read-onlyIdempotent

Query uploaded LoTW QSOs, confirmed or unconfirmed, and filter by persona, band, mode, or date range to inspect station activity.

Instructions

Query all uploaded QSOs from LoTW (confirmed and unconfirmed).

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": "lotw_qsos"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandNoFilter by band (e.g., '20M').
modeNoFilter by mode (e.g., 'FT8').
sinceNoQSOs uploaded since this date (YYYY-MM-DD). Default: last 30 days.
personaYesPersona name configured in adif-mcp.
end_dateNoQSO date range end (YYYY-MM-DD).
start_dateNoQSO date range start (YYYY-MM-DD).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds that both confirmed and unconfirmed QSOs are included, but does not mention authentication/persona needs, pagination, or the default last-30-days window.

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 zero wasted words. It is appropriately sized for a tool whose detailed parameter semantics are fully covered by the schema.

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

Completeness3/5

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

The output schema and annotations cover return shape and safety behavior, and the input schema documents all parameters. However, the description says 'all uploaded QSOs' while the schema notes a default last-30-days window, and the description gives no routing guidance among several sibling LoTW tools.

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 six parameters are already documented with examples and date formats. The description adds no parameter-level meaning beyond the schema, which is the expected baseline when schema coverage is complete.

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 and resource: query uploaded QSOs from LoTW. The parenthetical 'confirmed and unconfirmed' gives useful scope and partially distinguishes it from lotw_confirmations, though it does not explicitly name sibling tools.

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?

Provides no explicit guidance on when to use this tool versus lotw_confirmations, lotw_dxcc_credits, lotw_download, or lotw_user_activity. The query wording implies a general listing use case, but alternatives and exclusions are absent.

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