Skip to main content
Glama
Sign In
uni-t-uts-mcp

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_sweep

Idempotent

Configure sweep points, sweep time, sweep type, trigger source, and video trigger level for UNI-T UTS spectrum analyzers, with automatic coupling and warning reports for clamped values.

Instructions

Set sweep points, sweep time, sweep type, trigger source and video trigger level. Points, type and rule are applied before the sweep time so a manual time is not overridden by the auto coupling. Changing sweep_points changes the trace length. Out-of-range values are clamped silently by the instrument; settings are re-read afterwards and any change is 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_sweep"
  }
}

Input Schema

NameRequiredDescriptionDefault
instrumentNoWhich instrument to use (a name from list_instruments). Default: the `default` instrument, or the only one configured
sweep_typeNoSweep type (turns automatic type off)
sweep_pointsNoSweep points, integer 11..40001. Changes the trace length (trace data has this many values)
sweep_time_sNoSweep time in seconds (1 ms..4000 s, clamped; zero span allows less). Turns sweep time auto off
trigger_sourceNoTrigger source: immediate (free run) or video. External is rejected by the UTS3036B
sweep_time_autoNoAutomatic sweep time; not with sweep_time_s
sweep_time_ruleNoAutomatic sweep time rule
sweep_type_autoNoAutomatic sweep type; not with sweep_type
trigger_video_level_dbmNoVideo trigger level in dBm (clamped to -170..30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: points, type, and rule are applied before sweep time so manual timing is not overridden by auto coupling; changing sweep_points changes trace length; out-of-range values are silently clamped; and settings are re-read afterward with changes reported in warnings. These are exactly the kind of side effects and ordering rules an agent needs before mutating instrument state.

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 description is four short sentences and front-loads the tool purpose before behavioral details. It is efficient overall, though it repeats some schema information such as clamping and the effect of sweep_points on trace length.

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 nine-parameter, optional-parameter mutation tool with annotations and no output schema, the description covers purpose, ordering rules, side effects, clamping, and warning reporting well. It could be slightly more complete by explicitly addressing conflicts such as sweep_time_auto vs sweep_time_s, but the schema already states some of that constraint.

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 description coverage is 100%, so the schema already documents ranges, enums, and most per-parameter meanings. The description adds cross-parameter semantics, especially the ordering interaction between sweep points/type/rule and sweep time, plus the trace-length effect of sweep_points and the clamping/warning behavior. It does not add much for the instrument parameter, but it meaningfully supplements the schema overall.

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?

The description starts with a specific verb and enumerates the resources being configured: sweep points, sweep time, sweep type, trigger source, and video trigger level. It is clear what the tool does, but it does not explicitly differentiate itself from siblings such as get_sweep or single_sweep.

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?

Usage is implied by the configuration verb and the fact that it sets sweep parameters, but the description gives no explicit when-to-use guidance, no exclusions, and no named alternatives. An agent can infer that this configures sweep behavior rather than reads it or starts a sweep, but the routing is left implicit.

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

Deploy Server

Other Tools