uni-t-uts-mcp

set_trace

Idempotent

Configure a spectrum analyzer trace by selecting it, setting its type, live/hold and display state, plus global averaging; warnings report any settings the instrument rejected.

Instructions

Set trace configuration: select the current trace, and for one trace set its type (write, average, max_hold, min_hold), update state (live or view/hold) and display state, and set the global average count (1-999) and average type. Everything is re-read afterwards and anything the instrument did not take is reported in 'warnings'. Changing a trace type or the averaging restarts that trace's hold/average. To restart hold or averaging without changing settings use restart_trace.

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

Input Schema

Name	Required	Description
`type`	No	Trace type of `trace`: write (clear/write, live), average, max_hold or min_hold
`trace`	No	Trace (1-6) that type, update and display apply to
`update`	No	Update state of `trace`: true = live, false = view/hold (frozen)
`display`	No	Show (true) or hide (false) `trace`
`instrument`	No	Which instrument to use (a name from list_instruments). Default: the `default` instrument, or the only one configured
`average_type`	No	Average type (global): voltage, power or log
`average_count`	No	Average count, integer 1-999. Global: shared by every trace of type average
`selected_trace`	No	Make this trace (1-6) the current trace (:TRACe:SELect)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true), the description discloses that settings are re-read afterwards, that rejected settings surface in a 'warnings' field, and that changing a trace type or the averaging resets that trace's hold/average. The side-effect disclosure is the most valuable part and is genuinely non-obvious. What it omits is the shape of the response beyond 'warnings', which is minor with no output schema.

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 opening sentence is front-loaded with what the tool does, followed by two sentences on side effects and the alternative. Every sentence earns its place, though the first sentence is a dense compound list that could be split for easier scanning.

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?

With eight optional parameters, no output schema and minimal annotations, the description still covers which settings are affected, which are global versus per-trace, what happens on rejection, and where to go for a pure restart. Nothing an agent needs in order to call it correctly is missing.

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?

Schema description coverage is 100% and all eight parameters are already documented, including enum values and the 1-999 range. The description largely restates those fields (type list, live/view mapping, 1-999 count) rather than adding syntax or interaction rules the schema lacks, so the baseline of 3 applies.

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 names a specific verb and resource ('Set trace configuration') and then enumerates the exact settings it touches: selected trace, trace type, update state, display state, global average count and average type. It also distinguishes the write from restart_trace, so an agent can tell the two apart without opening 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It routes the agent explicitly: 'To restart hold or averaging without changing settings use restart_trace.' That is a named alternative plus the condition that selects it, which is the strongest form of guidance available here.

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

Deploy Server