Skip to main content
Glama
Sign In
omiss-mcp

omiss-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Omiss Checkin History

omiss_checkin_history
Read-onlyIdempotent

Lists past OMISS nets newest first, letting you filter by callsign, OM number, band, date, or net control to find when a station checked in or who ran a net.

Instructions

List past OMISS nets, newest first: all of them, or only those a member checked in to, on a band, on a date, or run by a net control. omiss.net shows the latest 100 matches.

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

Input Schema

NameRequiredDescriptionDefault
bandNoOnly nets on this band: 10m, 12m, 15m, 17m, 20m, 40m, 80m or 160m.
dateNoOnly nets on this date: YYYY, YYYY-MM or YYYY-MM-DD (UTC).
callsignNoOnly nets this station checked in to (e.g. KI7MT).
om_numberNoOnly nets this OMISS member checked in to (e.g. 7212).
net_controlNoOnly nets this station ran as net control.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the description correctly focuses on non-obvious behavior: results are ordered newest first, and the upstream site caps results at the latest 100 matches. That result-cap disclosure is genuinely valuable context an agent cannot get from annotations or schema. It stops short of describing what an empty result or a truncated page looks like.

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, front-loaded with the core action and ordering, with the filter list and the 100-result caveat following logically. No filler, though the mid-sentence filter enumeration ('on a band, on a date, or run by a net control') reads slightly list-like rather than prose.

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 needn't explain return shape, and it covers the pieces that matter for correct invocation: ordering, the optional-filter model, and the upstream result cap. A note on whether omitted filters mean 'all' vs 'most recent' would close the remaining gap.

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 every parameter (band, date, callsign, om_number, net_control) is already documented with formats and examples. The description only restates the filter concepts at a higher level and adds no format, precedence, or combination rules beyond the schema, 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?

Opens with a specific verb and resource ('List past OMISS nets') plus ordering ('newest first'), and enumerates the filter dimensions, which separates it from omiss_net_checkins (check-ins for a single net) and omiss_net_schedule (upcoming nets). It never names those siblings, so the differentiation is implicit rather than explicit.

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 'all of them, or only those...' makes clear that filters are optional and combinable, which is useful usage context. However there is no guidance on when to prefer this over omiss_net_checkins or omiss_net_statistics, and no mention of what happens with zero filters beyond the default listing.

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