Skip to main content
Glama
Sign In
n1mm-mcp

n1mm-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

N1Mm Clock

n1mm_clock
Read-onlyIdempotent

Track contest timing, off-time, and QSO/score pacing in one view, using station, duration, and target inputs to keep your operating schedule on plan.

Instructions

Contest clock — timing, off-time, and pacing in one view.

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

Input Schema

NameRequiredDescriptionDefault
target_qsosNoTarget QSO count for pacing.
station_nameNoStation to query.
target_scoreNoTarget score for pacing.
duration_hoursNoContest length (e.g., 48 for CQ WW, 24 for ARRL DX).
min_gap_minutesNoMinimum gap to count as off-time (default 30).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare this as a read-only, idempotent, non-destructive open-world query. The description only restates the title's concepts ('timing, off-time, and pacing') and adds no behavioral context such as how min_gap_minutes affects off-time calculation, whether results are cached, or what the clock view includes beyond the obvious.

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

Conciseness3/5

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

The description is a single short phrase and front-loaded, but it is under-specified rather than genuinely concise. Every word earns its place in the sense that there are no wasted sentences, but the phrase carries too little information for a five-parameter tool.

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

Completeness2/5

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

Although an output schema and annotations exist, the description does not explain the relationship to sibling tools, how to use the pacing targets, or what practical view the clock returns. For a tool with optional configuration parameters and several related status tools, this leaves meaningful gaps.

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%, so all five parameters are documented in the schema itself, including target_qsos, target_score, duration_hours, station_name, and min_gap_minutes. The description adds no parameter meaning beyond what the schema provides; baseline 3 is appropriate.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (contest clock) and three concepts (timing, off-time, pacing), which gives a rough idea of what the tool shows. However, it stops short of a specific verb or outcome, and it does not distinguish this from siblings like n1mm_current_state or n1mm_performance that likely overlap with timing/status views.

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 guidance about when to use this clock versus n1mm_current_state, n1mm_performance, or other status-oriented siblings. The phrase 'in one view' hints at a consolidated display but does not state a selection condition or exclusion.

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