n1mm-mcp

Overview Schema Source Related Servers Discussions Admin

N1Mm Bandmap

n1mm_bandmap

Read-onlyIdempotent

Retrieve live N1MM bandmap spots, unworked multipliers, and per-band activity counts to identify contest targets; filter results by band, mode, callsign prefix, or multipliers only.

Instructions

Live bandmap — spots, mult targets, and activity summary.

Returns active spots (with TTL eviction), unworked multipliers, and per-band spot activity counts in one snapshot.

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

Input Schema

Name	Required	Description
`band`	No	Filter by band (e.g., "20m").
`mode`	No	Filter by mode.
`callsign`	No	Search by callsign prefix.
`mults_only`	No	If true, only return spots flagged as multipliers.
`station_name`	No	Station to query.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.6Sep 28, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the description adds genuinely new traits: TTL eviction of spots (ephemeral data, results change between calls) and 'one snapshot' semantics. It omits pagination or size limits, which is a minor gap given the annotation coverage.

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 compact sentences, with the resource identity front-loaded and the returned contents immediately after. No filler.

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 an output schema present, the description only needs to convey what the tool is and how it behaves; it covers snapshot semantics and TTL eviction well. The remaining gap is routing versus the multipliers sibling.

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 all five filter parameters are documented there. The description only implies that band/mode/callsign filters shape the returned spot set, adding no syntax or interaction detail beyond the schema. 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?

States a specific resource (live bandmap) and enumerates its contents: spots, mult targets, activity summary. However, it does not distinguish this from the sibling n1mm_multipliers, despite overlapping output ('unworked multipliers'), so an agent cannot fully separate them from the description alone.

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?

The word 'Live' implies a real-time usage context, but there is no explicit guidance on when to use this instead of n1mm_multipliers, n1mm_pileup, or n1mm_contacts. No prerequisites or exclusions are stated.

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

Deploy Server