uni-t-uts-mcp

enter_analog_demod

Switch the analyzer to analog demodulation mode, saving frequency, bandwidth, sweep, and continuous-sweep settings for restoration. Warns if the module does not change; exit when done.

Instructions

Switch to the analog demodulation (AD) module and read it back. From spectrum analyzer mode, saves the frequency, bandwidth, sweep time and continuous-sweep settings first, for exit_analog_demod to restore; re-entering AD while already there keeps whatever was saved the first time. Warns (not an error) if the module did not change: on this firmware an unlicensed module is refused silently with no SCPI error, which this tool cannot distinguish from a link glitch. Leaves the instrument in AD on purpose; call exit_analog_demod when done. Does not select or preset an AM/FM demodulation type.

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": "enter_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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 13, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Far exceeds the single readOnlyHint=false annotation: it discloses the settings snapshot taken for later restore, the silent-refusal behavior for unlicensed modules, the deliberate warning-not-error on no-change, and that the instrument is intentionally left in AD. It even flags a diagnostic limitation (cannot distinguish refusal from a link glitch), which an agent needs to interpret the result correctly.

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?

Front-loaded with the action, then the side effects and warnings in a logical order. Dense but nearly every clause carries operational meaning; the parenthetical caveat about link glitches is slightly wordy but justified by its diagnostic value.

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?

Covers side effects, restoration contract, failure modes, and exit path for a state-changing tool with no output schema. The one gap is that "read it back" is never expanded — an agent doesn't know what state is returned — though the settings it captures are itemized.

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?

The single `instrument` parameter has full schema coverage, so the baseline applies. The description never mentions the parameter, but the schema's defaulting rules (default instrument, or the only one configured) are already documented there, so little is lost.

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 and resource ("Switch to the analog demodulation (AD) module and read it back") and immediately pairs it with its inverse, exit_analog_demod. The scope limits ("does not select or preset an AM/FM demodulation type") further separate it from sibling demod tools.

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 the entry condition ("From spectrum analyzer mode"), the exit action ("call exit_analog_demod when done"), and the exclusion (does not configure demodulation type). The re-entry case ("re-entering AD while already there keeps whatever was saved the first time") tells the agent what happens on a repeat call.

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

Deploy Server