Skip to main content
Glama
Sign In
n1mm-mcp

n1mm-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

N1Mm Performance

n1mm_performance
Read-onlyIdempotent

Retrieve a complete N1MM contest performance snapshot with score, rolling rates, band and mode breakdowns, hourly timeline, and run versus S&P stats to guide operating decisions.

Instructions

Complete performance snapshot — score, rate, bands, run/S&P, timeline.

Returns score, rolling rates (10m/30m/60m), rate derivative for band exhaustion detection, per-band breakdown, per-mode breakdown, hourly summary, and run vs S&P stats in one coherent 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_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandNoFilter rate/breakdown to specific band.
modeNoFilter to specific mode.
station_nameNoStation to query.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds domain context — notably that the rate derivative is intended for band-exhaustion detection — but says nothing about cost, latency, or behavior when filters are omitted. Since an output schema exists, its enumeration of returned fields is largely duplicative.

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 sentences, well front-loaded with the summary claim first and details second. The long field enumeration in sentence two overlaps the output schema and is the main trimming candidate, but it is not padded or redundant internally.

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?

The description adequately conveys the aggregate nature of the tool, and the output schema plus rich annotations carry the return shape and safety semantics. The one real gap is default scope: with three optional filters and zero required parameters, it never says what is returned when no band/mode/station is supplied.

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 three filters (band, mode, station_name) are documented inline, so the description has no compensation burden. It nonetheless never mentions the filters at all and instead presents the tool as 'complete', which slightly obscures that results can be scoped.

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?

Specific verb-and-resource framing: 'Complete performance snapshot' with an enumeration of what is aggregated (score, rate, bands, run/S&P, timeline). An agent can tell it's an aggregate analytics view rather than a raw-data tool. It does not explicitly differentiate itself from the closest sibling, n1mm_current_state, which an agent could plausibly confuse with a performance/rate snapshot.

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

Usage Guidelines3/5

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

The phrase 'in one coherent view' implies this is the consolidated alternative to calling several narrower tools, but no explicit when-to-use, when-not-to-use, or named alternative is given. With eleven siblings including n1mm_current_state, n1mm_diagnostics and n1mm_contacts, the choice is left to inference.

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