uni-t-uts-mcp

exit_measurement

Idempotent

Return to spectrum analyzer mode after a measurement, restoring saved frequency, bandwidth, sweep, and tracking-generator settings unless restoration is disabled.

Instructions

Leave the measurement and return to spectrum analyzer mode (:CONFigure:SANalyzer). The measurement preset leaves the span, RBW and sweep time changed, so unless restore_settings=false the frequency, bandwidth, sweep time and continuous-sweep settings saved by configure_measurement are put back and verified, and so is the tracking generator output, level and offset when it was on (a measurement entered elsewhere has nothing saved: a warning says so). Does nothing when already in spectrum analyzer mode.

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_measurement"
  }
}

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 the measurement was entered (default true)

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?

Goes well past the annotations (readOnlyHint=false, idempotentHint=true) by naming exactly which settings are restored and verified (frequency, bandwidth, sweep time, continuous sweep, tracking generator output/level/offset), disclosing the warning when nothing was saved, and confirming the no-op condition consistent with idempotency.

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?

The primary action is front-loaded in the first sentence, and the remaining sentences carry substantive edge-case detail. The long middle sentence with parentheticals is dense but not padding.

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?

For a two-parameter mutation with no output schema, it covers the side effects, the failure/warning path, and the no-op case. Only the shape of the returned confirmation is left implicit.

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, but the description adds real meaning for restore_settings by specifying what is restored when true and that the restore is verified. The instrument parameter is left entirely to the schema.

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 target ("Leave the measurement and return to spectrum analyzer mode") and anchors it to the SCPI command :CONFigure:SANalyzer. It is clearly distinct from configure_measurement and enter_analog_demod, which do the opposite.

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?

Explains the restore_settings=true default and what setting it to false does, plus the no-op case when already in spectrum analyzer mode. It references configure_measurement as the pairing counterpart, but does not explicitly route the agent to a sibling for entering measurements.

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

Deploy Server