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

switch_config

Activate an existing WSJT-X configuration without transmitting.

Instructions

Switch WSJT-X to a named configuration (which must already exist). No transmit.

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": {
      "name": "<name>"
    },
    "name": "switch_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
instanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/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 tool does not cause transmission but does not mention error handling for missing configurations, effects on current operation, or any side effects. Minimal behavioral disclosure.

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?

Two sentences with no wasted words. The action verb 'Switch' is the first word, and all information is front-loaded.

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

Completeness2/5

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

Given the tool has two parameters, no output schema, and no annotations, the description is too brief. It lacks details on return values, behavior when the configuration is missing, and what 'no transmit' means in the broader context of WSJT-X operation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It explains the 'name' parameter as the named configuration, but does not mention the optional 'instance' parameter or its purpose. Partial coverage.

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 uses a specific verb ('Switch') and resource ('WSJT-X to a named configuration') and explicitly states that the configuration must already exist, distinguishing it from sibling tools like 'configure' which likely creates or edits configurations. The scope is clear.

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?

The description implies when to use the tool (to switch to an existing configuration) and includes a behavioral note ('No transmit') but does not explicitly state when not to use it or provide direct alternatives among siblings.

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