Skip to main content
Glama
Sign In
io.github.sbrunner-atx/wsjtx-mcp

io.github.sbrunner-atx/wsjtx-mcp

by sbrunner-atx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

transmit

Stop sending immediately or at the end of the current transmission period.

Instructions

Stop transmitting. (WSJT-X's UDP protocol can halt but cannot enable Tx.)

operations:

  • halt: stop immediately (takes you off the air now).

  • halt_auto: stop at the end of the current transmission period.

Always allowed — halting only ever takes you off the air. To start a transmission use reply (answer a CQ) or free_text with send=true.

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

Input Schema

NameRequiredDescriptionDefault
instanceNo
operationNohalt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that the UDP protocol can halt but not enable Tx, and explains the two operation behaviors. However, it does not mention any required permissions or side effects beyond taking off the air.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured with a core statement followed by bullet points. Every sentence adds value, and it is front-loaded with the primary function.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description adequately covers the tool's purpose and operations given its low complexity (2 params, no output schema). However, it fails to explain the 'instance' parameter, which may be important for context, leaving a completeness 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 coverage is 0%, so description must compensate. It explains the 'operation' parameter with two values and their effects, but does not explain the 'instance' parameter at all. Partial coverage leaves a gap.

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?

The description clearly states the tool stops transmission, specifying two operations. It distinguishes from sibling tools 'reply' and 'free_text' which start transmission. However, the tool name 'transmit' may mislead, but the description clarifies the actual purpose.

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 states when to use this tool (to stop transmission) and when to use alternatives ('reply' or 'free_text' to start). Also notes that halting is always allowed, providing clear guidance.

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