uni-t-uts-mcp

exit_analog_demod

Switch the analyzer from analog demodulation back to spectrum-analyzer mode and restore saved frequency, bandwidth, and sweep settings when requested.

Instructions

Leave the AD module and return to spectrum analyzer mode (:INSTrument:SELect SA). Unless restore_settings=false, the frequency, bandwidth, sweep time and continuous-sweep settings saved by enter_analog_demod are put back and verified by read-back (the same resend-once-then-fail pattern exit_measurement uses). Always sends the switch, even if this server never called enter_analog_demod (e.g. after select_instrument_module); a clear warning says so when there is nothing saved to restore, rather than guessing at settings this server never saw.

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

Input Schema

Name	Required	Description	Default
`instrument`	No	Which instrument to use (a name from list_instruments). Default: the `default` instrument, or the only one configured
`restore_settings`	No	Restore the settings saved when AD was entered (default true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint=false/idempotentHint=false annotations, it discloses what is actually restored (frequency, bandwidth, sweep time, continuous-sweep), that restoration is verified by read-back with a resend-once-then-fail retry pattern, and that a clear warning is emitted when nothing was saved. That is exactly the operational context an agent needs before calling a state-mutating exit.

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?

Purpose is front-loaded in the first clause and the remaining sentences each carry distinct information (restore behavior, retry pattern, no-saved-state warning). It is a dense paragraph rather than a bulleted structure, but no sentence is filler.

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?

For a two-parameter state-switching tool with no output schema, the description covers trigger conditions, side effects, verification behavior, and the edge case where no state was previously saved. Nothing material is left for the agent to guess.

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%, so the baseline is 3; the description still adds value by enumerating which settings restore_settings governs and by confirming the default-true semantics. The instrument parameter is left to the schema, which already documents its default resolution.

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 opens with a specific verb+resource: 'Leave the AD module and return to spectrum analyzer mode', and even gives the SCPI command (:INSTrument:SELect SA). It is unmistakably the inverse of the sibling enter_analog_demod, so an agent can distinguish the pair without inspecting either schema.

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?

It states the entry condition (after AD work, including when the module was selected via select_instrument_module) and explains when restore_settings should be false, plus that the switch is always safe to send. It stops short of naming an explicit alternative tool for leaving a non-AD measurement, but the usage context is clear.

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

Deploy Server