Skip to main content
Glama
Sign In
omiss-mcp

omiss-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Omiss Net Schedule

omiss_net_schedule
Read-onlyIdempotent

Retrieve the OMISS net schedule, including each net's band, UTC time, frequency, operating window, days, holiday details, band coordinator, and next run time.

Instructions

Get the OMISS net schedule: every net's band, UTC time, frequency and window, days, holiday time and band coordinator, and the next time it runs; the schedule's footnotes (holidays, winter schedule); and the federal holiday dates the holiday schedule follows. Days and times are UTC, so an evening net in the Americas falls on the previous local day; use next_utc and as_of_utc to work out "today" in the user's time zone. next_utc is the listed start: nets often open early for check-ins, and a net on the air now shows next_utc as its next run, so ask omiss_nets_on_air whether one is open.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered by structured data. The description adds non-obvious behavior the annotations cannot: next_utc is the listed start rather than actual open time, nets often open early for check-ins, and an in-progress net still reports next_utc as its next run. That is high-value operational context.

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?

Content is front-loaded: the resource and return payload come first, then timezone caveats, then the sibling routing. The first sentence is long and clause-dense, but nearly every clause carries information that changes how an agent uses the result.

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

Completeness5/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 need not describe return values, and it doesn't waste words doing so. For a parameterless, read-only tool it covers the remaining risks — UTC versus local day boundaries and the sibling that answers on-air status — so an agent can call it and interpret results correctly.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It still usefully explains how to interpret the returned time fields (next_utc, as_of_utc) for local-date reasoning, which is field semantics rather than parameter semantics.

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?

A specific verb and resource ('Get the OMISS net schedule') followed by an inventory of exactly what is returned: band, UTC time, frequency, window, days, holiday time, coordinator, next run, footnotes, and federal holidays. This is distinguishable at a glance from siblings like omiss_nets_on_air or omiss_net_statistics.

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

Usage Guidelines5/5

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

Explicitly routes the agent to the alternative: 'ask omiss_nets_on_air whether one is open' when the question is about whether a net is currently on the air. It also names the condition that selects the alternative (a net on air now shows next_utc as its next run), which is exactly the routing detail an agent needs.

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