Skip to main content
Glama
eqsl-mcp

eqsl-mcp

by qso-graph

Eqsl Ag Check

eqsl_ag_check
Read-onlyIdempotent

Check whether a callsign has Authenticity Guaranteed (AG) status on eQSL using a cached member list, enabling AG verification without authentication.

Instructions

Check if a callsign has Authenticity Guaranteed (AG) status on eQSL.

Public, no auth required. Uses a cached copy of the AG member list (refreshed every 4 hours).

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

Input Schema

NameRequiredDescriptionDefault
callsignYesThe callsign to check.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context beyond annotations: no authentication is required, and results come from a cached AG list refreshed every 4 hours, which tells the agent the data may be slightly 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?

The description is short, front-loaded with the primary purpose, and every sentence adds useful context. The public/no-auth note and cache refresh detail are directly relevant and not redundant.

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

Completeness5/5

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

For a simple one-parameter lookup with an output schema, the description covers the key behavioral context: it is public, requires no auth, and uses a cached list refreshed every four hours. Return values are covered by the output schema, so no further explanation is needed.

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?

There is only one parameter, and the schema already documents it at 100% coverage as 'The callsign to check.' The description adds no additional format, validation, or syntax details beyond what the schema provides, so the baseline of 3 is appropriate.

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

Purpose5/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: checking whether a callsign has Authenticity Guaranteed (AG) status on eQSL. That AG-status scope distinguishes it from sibling tools like eqsl_verify, eqsl_inbox, and eqsl_download without needing to name them explicitly.

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 description makes the tool's purpose clear and notes that it is public with no auth required, which implies appropriate usage. However, it does not explicitly say when to use this instead of related siblings such as eqsl_verify, nor does it state exclusions.

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