uni-t-uts-mcp

set_ad_demod_timing

Idempotent

Configure demodulation window sweep time, demodulation time (manual or automatic), and averaging state/count for an active AD module on UNI-T UTS spectrum analyzers.

Instructions

Configure the AD module's demodulation window sweep time, demodulation time (or automatic), and averaging state/count. AD module must be active. The AM/FM prefix is read fresh from :CONFigure? each call. Ranges come from the programming manual and are not yet live-verified. Everything requested is re-read afterwards and any instrument-adjusted value is reported in 'warnings'. Leaves the new state (nothing is restored).

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

Input Schema

Name	Required	Description
`instrument`	No	Which instrument to use (a name from list_instruments). Default: the `default` instrument, or the only one configured
`demod_time_s`	No	Demodulation time in seconds (manual gives no upper bound; auto is 36x the window sweep time)
`average_count`	No	Average count, 1 to 999 (manual)
`average_state`	No	Averaging on/off
`demod_time_auto`	No	Automatic demodulation time on/off
`window_sweep_time_s`	No	Demodulation window sweep time in seconds, 1 us to 500 ms (manual)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 13, 2026

TDQS

A3.8/5.0

Behavior4/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 context beyond that: the AM/FM prefix is re-read from :CONFigure? on every call, requested values are re-read afterwards with instrument-adjusted values surfaced in 'warnings', and the new state is left in place with nothing restored. It also honestly flags that ranges come from the manual and are not live-verified — a rare and valuable reliability caveat.

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 and the parameters it touches, then the prerequisite, then caveats. Five short sentences, none padded. The final 'Leaves the new state (nothing is restored)' is slightly redundant phrasing of one idea but still earns its place as a persistence disclosure.

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 6-parameter mutation tool with no output schema, the description covers the prerequisite, the device-side re-read behavior, the shape of returned warnings, uncertainty in documented ranges, and post-call state. An agent has everything needed to invoke it correctly and interpret the result.

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 coverage is 100% and every parameter already carries a description including ranges and the auto=36x-window relationship, so the description's parameter mentions are largely restatement. It does clarify that demod time and auto are alternatives, but adds no syntax, units, or interaction detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Configure) and a precisely bounded resource: the AD module's demodulation window sweep time, demodulation time/auto, and averaging state/count. The scope is narrow enough to distinguish it from generic siblings like set_ad_display or set_ad_filters, though it never names an adjacent tool to contrast with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Provides one hard prerequisite ('AD module must be active'), which is genuinely useful usage context. However it gives no guidance on when to prefer this over related tools, and it doesn't point to the sibling that activates the AD module, leaving the precondition as an implied chore rather than an actionable route.

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

Deploy Server