Skip to main content
Glama
iota-mcp

iota-mcp

by qso-graph

Iota Dxcc

iota_dxcc
Read-onlyIdempotent

Map DXCC entity numbers to IOTA groups or IOTA references to their DXCC entities. Provide a DXCC number or IOTA refno to retrieve the corresponding cross-reference.

Instructions

Bidirectional DXCC-to-IOTA mapping.

Provide either dxcc_num to find all IOTA groups for a DXCC entity, or refno to find which DXCC entities an IOTA group belongs to.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "iota_dxcc"
  }
}

Input Schema

NameRequiredDescriptionDefault
refnoNoIOTA reference number (e.g., EU-005).
dxcc_numNoDXCC entity number (e.g., 291 for USA, 223 for England).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds useful behavioral context by tying each parameter to a different result direction, though it does not clarify precedence when both or neither parameters are supplied.

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?

Two tight sentences front-load the bidirectional mapping purpose and then explain parameter selection. There is no redundant or filler text.

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 annotations, full schema coverage, and an output schema, the description is nearly complete for invocation. The only notable gap is that it does not specify behavior when both parameters are provided or when neither is provided.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by stating what each parameter returns: all IOTA groups for dxcc_num, or DXCC entities for refno. Examples and format details remain in the schema.

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 resource and operation: bidirectional DXCC-to-IOTA mapping. It clearly explains both directions of the mapping, which distinguishes it from generic sibling lookup/search tools.

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

Usage Guidelines4/5

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

It explicitly tells the agent which parameter to provide for each lookup direction: dxcc_num for DXCC-to-IOTA, refno for IOTA-to-DXCC. It does not name sibling alternatives or exclusions, but the primary usage path is clear.

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