uni-t-uts-mcp

set_tracking_generator

Idempotent

Configure tracking generator output: set on/off, level (dBm), offset, reference trace, and normalization reference level; turn it off when done to restore automatic RBW/VBW.

Instructions

Set the tracking generator (trace source): output on/off, level (dBm), level offset (dB), reference trace, normalization and its reference level. Level and offset are set before the output is switched on. The output is wired to the analyzer input on some benches, so switch it off when done: switching it off also re-asserts automatic RBW/VBW that were on (the instrument otherwise keeps a stale 300 kHz RBW). Values the instrument changed are reported in 'warnings'.

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

Input Schema

Name	Required	Description
`enabled`	No	Tracking generator output on or off
`level_dbm`	No	Output level in dBm (-40 to 0 on the UTS3036B)
`normalize`	No	Normalization on or off
`instrument`	No	Which instrument to use (a name from list_instruments). Default: the `default` instrument, or the only one configured
`level_offset_db`	No	Output level offset in dB (-200 to 200)
`reference_trace`	No	Reference trace on or off (only takes while the output is on)
`normalize_ref_level_db`	No	Normalization reference level in dB (-100 to 100)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 13, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false and idempotentHint=true; the description adds substantial behavior beyond that: internal ordering (level/offset applied before enabling output), a physical wiring caveat that the output feeds the analyzer input on some benches, and the side effect that disabling re-asserts automatic RBW/VBW because the instrument otherwise retains a stale 300 kHz RBW. It also discloses that changed values are surfaced in a 'warnings' field, which is crucial given there is 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Opens with purpose and the parameter inventory, then front-loads the ordering rule and the wiring/RBW warning, and closes with the return-value note. Five dense sentences, none redundant, and the critical 'switch it off when done' caveat is prominent rather than buried.

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?

Seven optional parameters, no output schema, and idempotent set semantics — the description covers ordering, hazards, side effects, and even names the 'warnings' return field, which is more than most setters provide. It could still say what happens when no parameters are supplied (no-op vs. reset), but nothing essential for correct invocation 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%, so every parameter (including ranges like -40 to 0 dBm and the 'only takes while the output is on' note on reference_trace) is already documented in the schema; baseline is 3. The description adds only cross-parameter ordering semantics and groups normalization with its reference level, which is a modest value-add rather than new per-parameter meaning.

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 ('Set the tracking generator') and immediately enumerates the exact controllable facets: output on/off, level, level offset, reference trace, normalization and its reference level. These map one-to-one onto the schema properties, so an agent can tell precisely what the tool mutates and distinguish it from the read-side get_tracking_generator sibling.

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?

Gives concrete operational context: 'Level and offset are set before the output is switched on' and 'switch it off when done', which tells the agent how to sequence calls. It does not name alternatives or state when not to use this tool (e.g. versus get_tracking_generator for read-only inspection), so it stops short of full routing guidance.

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

Deploy Server