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

uni-t-uts-mcp

by Reid-n0rc

configure_measurement

Idempotent

Enter a measurement such as channel power, OBW, ACPR, or harmonics and set its parameters; the analyzer stays in that mode and restores prior settings on exit.

Instructions

Enter a measurement (channel_power, time_power, obw, acpr, toi, cn or harmonics) and set its parameters; the instrument stays in the measurement until exit_measurement. preset=true (default) is :CONFigure:, false is :CONFigure::NDEFault. Either way the instrument changes the span, RBW and sweep time (for example span 3 MHz); when entered from spectrum analyzer mode the previous frequency, bandwidth and sweep settings are saved and exit_measurement puts them back, and so is the tracking generator output (entering a measurement switches it off). While a measurement is active most spectrum analyzer queries (detector, trace type) get no reply and the tracking generator cannot be changed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "measurement": "<measurement>"
    },
    "name": "configure_measurement"
  }
}

Input Schema

NameRequiredDescriptionDefault
xdbNoobw only: x dB level in dB, -100 to -0.1
presetNoPreset the measurement's parameters (default true)
averageNoMeasurement averaging on/off
percentNoobw only: occupied power fraction, above 0 up to 1 (0.99 = 99 %); the instrument clamps to 0.9999
offset_hzNoacpr or cn: offset of the adjacent channel (acpr) or of the noise (cn) from the carrier, in Hz, 0 or more
instrumentNoWhich instrument to use (a name from list_instruments). Default: the `default` instrument, or the only one configured
measurementYes
offset_sideNoacpr only: which adjacent channels to measure
average_typeNoAverage type
left_limit_sNotime_power only: left limit in s, 0-0.01 (10 ms)
sweep_time_sNoharmonics only: sweep time in s, 0.001-100
average_countNoAverages, integer 1-999 (manual range)
right_limit_sNotime_power only: right limit in s, 0-0.01 (10 ms)
fundamental_hzNoharmonics only: fundamental frequency in Hz
average_controlNoAverage termination control
harmonics_countNoharmonics only: number of results including the fundamental, integer 2-10 (the preset is 2)
noise_bandwidth_hzNocn only: noise bandwidth in Hz
carrier_bandwidth_hzNoacpr only: carrier (main channel) bandwidth in Hz
integration_bandwidth_hzNochannel_power, acpr or cn: integration bandwidth in Hz (channel_power: clamped by the instrument to 100 Hz..3.61 GHz)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.8/5.0
Behavior5/5

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

The annotations only declare readOnly=false and idempotent=true; the description goes far beyond by disclosing what is mutated (span, RBW, sweep time), that prior frequency/bandwidth/sweep settings and the tracking generator output are saved and restored by exit_measurement, and that the tracking generator is switched off on entry. It also warns about degraded behavior of other tools while a measurement is active — a major inter-tool side effect that no annotation conveys.

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 verb, resource, and preset semantics before moving into side effects, and nearly every clause carries operational information. The middle section is a long run-on chain of semicolon-joined clauses that could be broken into shorter sentences for readability, but no content is filler.

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 19-parameter, output-schema-less mutation tool, the description covers the essential unknowns: what state changes, what gets saved and restored, how preset maps to instrument commands, and how other tools behave while active. Parameter details are already handled by the 95%-covered schema, so nothing an agent needs to call this safely is missing.

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 95%, so the baseline is 3, but the description adds genuine meaning beyond the schema by mapping preset=true/false to the concrete :CONFigure:<meas> versus :CONFigure:<meas>:NDEFault commands and giving a concrete span example (3 MHz). It stops short of explaining the many measurement-specific parameters (xdb, percent, offset_hz), but those are well covered by the schema itself.

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 ('Enter a measurement') and enumerates the exact allowed measurement types (channel_power, time_power, obw, acpr, toi, cn, harmonics). It names the paired sibling exit_measurement, so the agent can distinguish this from lifecycle siblings like get_measurement or read_measurement without opening a 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?

Explicitly frames the enter/exit lifecycle ('the instrument stays in the measurement until exit_measurement') and names the exit tool as the terminating action. It also states the conditions under which this tool should be used with care — while a measurement is active, most spectrum analyzer queries return nothing and the tracking generator cannot be changed — which is exactly the when/when-not guidance an agent needs.

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