Skip to main content
Glama
lotw-mcp

lotw-mcp

by qso-graph

Lotw User Activity

lotw_user_activity
Read-onlyIdempotent

Check whether a callsign uses LoTW and find when it last uploaded, using a locally cached activity list refreshed weekly.

Instructions

Check if a callsign uses LoTW and when they last uploaded.

Public endpoint — no authentication required. Uses a locally cached copy of the LoTW user activity CSV (refreshed weekly).

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": {
      "callsign": "<callsign>"
    },
    "name": "lotw_user_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsignYesCallsign to check.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds meaningful behavioral details beyond those annotations: no authentication is required and data comes from a weekly-refreshed local cache, so results may be up to a week stale.

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, front-loaded with the purpose. Each sentence adds useful information: the lookup behavior, authentication status, and cache freshness.

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?

For a simple read-only lookup with an output schema, the description covers the essentials: what it checks, that no auth is needed, and that cached data is refreshed weekly. Minor gaps remain around how exact the callsign match must be and when to prefer sibling 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%, and the single parameter is already documented as 'Callsign to check.' The description does not add format, case-sensitivity, or other parameter semantics beyond what the schema provides, so baseline 3 is appropriate.

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: check whether a callsign uses LoTW and when it last uploaded. The purpose is clear, but it does not explicitly distinguish itself from siblings like lotw_qsos or lotw_confirmations.

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?

Provides useful usage context: public endpoint, no authentication, and locally cached CSV refreshed weekly. However, it does not state when to choose this tool over sibling alternatives such as lotw_confirmations or lotw_qsos.

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