Skip to main content
Glama
Sign In
n1mm-mcp

n1mm-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

N1Mm Contacts

n1mm_contacts
Read-onlyIdempotent

Retrieve a current N1MM Logger+ QSO log snapshot, including the last contact, filtered recent QSOs, recent edits, and deletes for contest monitoring.

Instructions

QSO log — recent contacts, edits, and deletes.

Returns the last QSO, filtered recent QSOs, recent edits, and recent deletes in one coherent 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_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandNoFilter by band (e.g., "20m").
modeNoFilter by mode (e.g., "CW").
countNoNumber of recent QSOs to return (default 10, max 100).
sinceNoISO timestamp — return only QSOs after this time.
call_patternNoFilter by callsign prefix.
station_nameNoStation to query (auto-detected if only one).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: the return is a composite snapshot combining last QSO, filtered QSOs, edits and deletes, which prevents misreading 'edits and deletes' as mutations. It says nothing about volume limits or snapshot consistency, though, so it is additive but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the resource label before the detail. There is mild redundancy between 'recent contacts, edits, and deletes' and the expansion that follows, but nothing is wasted enough to hurt.

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?

An output schema exists and all six parameters are documented, so the description needn't explain return shapes. What remains missing for correct selection is routing guidance against the many similarly named n1mm siblings — a meaningful gap for a tool in a crowded cluster.

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%, with band, mode, count, since, call_pattern and station_name each documented including the count default and 100 maximum. The description only alludes to filtering in general terms and adds no syntax or interaction semantics (e.g. how since combines with count), so 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?

The description names a specific resource (the QSO log) and enumerates exactly what is returned: the last QSO, filtered recent QSOs, recent edits, and recent deletes. It is clear what the tool does, but it never distinguishes itself from adjacent siblings such as n1mm_current_state, which an agent could reasonably assume also surfaces the last QSO.

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?

There is no statement of when to reach for this tool versus the other eleven n1mm_* tools, and no exclusions or prerequisites. The only hint is the word 'filtered', which implies the schema filters exist, but an agent must infer the selection criteria entirely on its own.

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

Deploy Server

Other Tools