Skip to main content
Glama
Sign In
omiss-mcp

omiss-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Omiss Set Callsign

omiss_set_callsign
Idempotent

Save the user's amateur radio callsign once to identify their station for OMISS nets on air; ask for it rather than guessing so NetLogger shares it correctly.

Instructions

Save the user's amateur radio callsign, for omiss_nets_on_air. Needed once.

NetLogger is told which station is asking. The callsign is shared with netlogger-mcp, if it's installed. Ask the user for their own callsign; don't guess it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "callsign": "<callsign>"
    },
    "name": "omiss_set_callsign"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsignYesThe user's callsign (e.g. KI7MT).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly=false, idempotent=true, destructive=false), so the description adds genuinely new context: NetLogger is informed which station is asking, and the value is shared with netlogger-mcp if installed. It also implies persistence rather than a per-call parameter. Return behavior is covered by the output schema.

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, front-loaded with the core action and the prerequisite. The NetLogger/mcp-sharing detail is secondary but earns its place by explaining a side effect.

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?

For a one-parameter idempotent setter with full schema coverage, an output schema, and annotations, the description supplies the prerequisite, the side effect, and the sourcing rule for the value. Only an explicit statement of change/reset semantics or permissions is absent.

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?

Schema coverage is 100% and the schema even supplies an example (KI7MT), so the baseline is 3. The description adds meaning beyond that by stressing the callsign must be the user's own and must not be guessed, which is a real correctness constraint on the value.

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?

States a specific verb+resource ("Save the user's amateur radio callsign") and scopes it to the target tool (omiss_nets_on_air). No sibling among the omiss_* lookup/report tools performs a write, so the distinction is unambiguous.

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

Usage Guidelines4/5

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

"Needed once" plus the tie to omiss_nets_on_air establishes a prerequisite and frequency, and "Ask the user for their own callsign; don't guess it" is an explicit behavioral instruction. It lacks a stated when-not-to-use case, so it falls short of a 5.

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