Skip to main content
Glama
Sign In
n1mm-mcp

n1mm-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

N1Mm Current State

n1mm_current_state
Read-onlyIdempotent

Retrieve a complete N1MM Logger+ station snapshot—connection status, contest details, operator callsign, and radio state—so an AI session can start with current live data.

Instructions

Complete station snapshot — connection, contest, operator, radios.

Returns connection status, contest info, operator callsign, and full radio state for Radio 1 (and Radio 2 if SO2R). This is the first tool any AI session should call.

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_current_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
station_nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the bar is lower. The description adds useful behavioral context by listing what the snapshot contains and noting that Radio 2 state is included only for SO2R.

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 two tight sentences, front-loaded with the core snapshot purpose and followed by return details and session-start guidance. Every sentence contributes materially.

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?

An output schema exists, so the description does not need to fully document return values, and the annotations cover safety behavior. The main remaining gap is that the optional station_name parameter is not explained.

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

Parameters2/5

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

Schema description coverage is 0%, and the only parameter, station_name, is never mentioned in the description. The phrase 'station snapshot' weakly implies station scoping, but it does not explain how station_name selects or affects the returned state.

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 gives a specific verb-and-resource framing: it returns a complete station snapshot covering connection, contest, operator, and radios. This clearly distinguishes it from narrower siblings such as n1mm_bandmap, n1mm_clock, or n1mm_so2r.

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 says this is the first tool any AI session should call, which gives strong usage context. It does not name when to use alternatives instead, but the 'first call' guidance is clear enough for a session-start snapshot tool.

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