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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_bandwidth

Idempotent

Configure RBW, VBW, VBW/RBW ratio, and filter shape on a UNI-T UTS spectrum analyzer; manual values disable auto flags and any clamped or coupled changes are reported.

Instructions

Set RBW, VBW, the VBW/RBW ratio and the filter shape. Manual values turn the matching auto flag off. The instrument snaps/clamps values and couples RBW, VBW and sweep time to the span and auto flags, so everything is 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_bandwidth"
  }
}

Input Schema

NameRequiredDescriptionDefault
rbw_hzNoResolution bandwidth in Hz; snaps to 1-3-10 steps and is clamped to 1 Hz..max (3 MHz on the UTS3036B). Turns RBW auto off
vbw_hzNoVideo bandwidth in Hz (1-3-10 steps, clamped like RBW). Turns VBW auto off
rbw_autoNoAutomatic RBW (follows the span); not with rbw_hz
vbw_autoNoAutomatic VBW (RBW times vbw_rbw_ratio); not with vbw_hz
instrumentNoWhich instrument to use (a name from list_instruments). Default: the `default` instrument, or the only one configured
filter_shapeNoResolution filter shape
vbw_rbw_ratioNoVBW/RBW ratio used while VBW is automatic (3e-5..3e6 on the UTS3036B; clamped)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

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

The description adds substantial behavior beyond annotations: the instrument snaps values to 1-3-10 steps and clamps them, couples RBW, VBW and sweep time to span and auto flags, re-reads everything afterwards, and reports changes in 'warnings'. That is exactly the side-effect and post-condition information an agent needs for a mutation call. It stops short of saying what happens when no parameters are supplied.

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?

Two sentences, front-loaded with the settable fields, followed by the behavioral consequences. No filler, and the most decision-relevant information (auto flags turn off) comes first.

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?

Strong for a 7-parameter, zero-required mutation tool with no output schema: the coupling, clamping and 'warnings' reporting fill the gaps an output schema would normally cover. The only omission is what happens on a no-argument call.

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 meaning the schema does not: that setting a manual value clears the corresponding auto flag and that RBW/VBW/sweep time are coupled to span, so changing one may silently move others. The 'warnings' return mention also signals that submitted values may not be the values applied.

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?

Opens with a precise verb plus an enumerated resource set: RBW, VBW, the VBW/RBW ratio and filter shape. An agent can immediately tell this is the write counterpart to a bandwidth read and which instrument settings it touches, without opening the schema.

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 rather than stated: 'Manual values turn the matching auto flag off' tells the agent about the auto/manual interaction, and the schema adds 'not with rbw_hz'. But there is no explicit when-to-use guidance, no mention of get_bandwidth as the read alternative, and no statement of when not to call it.

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