Skip to main content
Glama
Sign In
omiss-mcp

omiss-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Omiss Nets On Air

omiss_nets_on_air
Read-onlyIdempotent

Lists OMISS amateur-radio nets currently on the air from NetLogger, matching each to the OMISS schedule and identifying its scheduled net.

Instructions

List OMISS nets on the air now, from NetLogger, each matched to OMISS's own net schedule.

A net on NetLogger is an OMISS net when it matches a scheduled one (its frequency is in that net's window, on a day it runs, near its start time) or its name says OMISS. Each says which scheduled net it is.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the description is free to add value elsewhere — which it does by disclosing the data source (NetLogger) and the exact matching heuristic (frequency within window, correct day, near start time, or OMISS in the name). It does not mention refresh cadence or how stale the 'now' snapshot can be.

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?

Three short sentences, with the core purpose front-loaded before the matching explanation. The closing sentence ('Each says which scheduled net it is') is slightly redundant with the opening clause about matching to the schedule but does clarify the output shape.

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, return values need no explanation, and the description supplies source and matching logic. For a live-data tool it would be stronger with a note on snapshot freshness or the fact that results can be empty between nets.

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

Parameters4/5

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

Zero parameters, so there is nothing for the description to clarify and the baseline of 4 applies. The description correctly avoids inventing filter parameters that the empty schema does not support.

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?

States a specific verb and resource: list OMISS nets currently on the air, sourced from NetLogger and cross-matched to the OMISS schedule. This implicitly separates it from the static omiss_net_schedule and from checkin-oriented siblings, though it never names those siblings explicitly.

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 'on the air now' implies a real-time use case versus the static schedule, but there is no explicit when-to-use guidance, no statement of when to prefer omiss_net_schedule or omiss_net_checkins, and no exclusions or prerequisites.

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