io.github.sbrunner-atx/wsjtx-mcp

Overview Schema Source Related Servers Discussions Admin

configure

Configure WSJT-X parameters (mode, submode, frequency tolerance, T/R period, Rx DF, DX call/grid) via UDP without transmitting or changing dial frequency.

Instructions

Set operating parameters via a Configure message (no transmit).

Sets: mode, submode, frequency tolerance, fast mode, T/R period, Rx DF, DX call, DX grid, and whether to regenerate the standard messages. Empty string = "no change" for text fields; None = "no change" for the numeric fields.

IMPORTANT caveats:

There is no dial-frequency control over UDP. QSY is a rig-control concern (Hamlib/CAT or the WSJT-X UI), not this tool.
The protocol has no "no change" for the two booleans, so fast_mode and generate_messages are always sent (defaulting to false). Pass them explicitly if you care about their state.

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

Input Schema

Name	Required	Description	Default
`mode`	No
`rx_df`	No
`dx_call`	No
`dx_grid`	No
`submode`	No
`instance`	No
`fast_mode`	No
`tr_period`	No
`generate_messages`	No
`frequency_tolerance`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 27, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Discloses important behavioral details beyond the schema, such as 'no transmit', no dial-frequency control, and the mandatory sending of boolean parameters. With no annotations, this is valuable transparency.

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?

Well-structured with a summary sentence, parameter list, and bullet-point caveats. Slightly verbose but efficient for the complexity.

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?

Given 10 optional parameters, no output schema, and no annotations, the description provides sufficient context about what the tool does, its caveats, and parameter behavior. Lacks mention of the instance parameter and any return value, but overall adequate.

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?

Description lists most parameters and explains the 'no change' semantics for empty string and None. However, it omits the 'instance' parameter entirely, and schema coverage is 0%, so the description does not fully compensate.

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?

The description clearly states it sets operating parameters via a 'Configure' message and explicitly lists which parameters it controls. It distinguishes from sibling tools like 'transmit' by noting 'no transmit'.

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?

Includes explicit caveats about when not to use (no dial-frequency control) and how boolean parameters behave. Does not explicitly name alternative tools but provides clear context for appropriate use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server