uni-t-uts-mcp

set_frequency

Idempotent

Configures spectrum analyzer frequency settings using center/span, start/stop, full span, or zero span, then reports any instrument-adjusted values as warnings.

Instructions

Set frequency parameters (all in Hz). Give center and/or span, OR start and/or stop, OR full_span, OR zero_span; center step and offset can be combined with any of these. Frequency parameters are coupled, so the settings are re-read afterwards; 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_frequency"
  }
}

Input Schema

Name	Required	Description
`span_hz`	No	Span in Hz (> 0; use zero_span for zero span)
`stop_hz`	No	Stop frequency in Hz (> 0)
`start_hz`	No	Start frequency in Hz (>= 0)
`center_hz`	No	Center frequency in Hz (> 0)
`full_span`	No	Set the full span. Cannot be combined with center/span/start/stop
`offset_hz`	No	Frequency offset in Hz
`zero_span`	No	Set zero span (time domain). Cannot be combined with center/span/start/stop
`instrument`	No	Which instrument to use (a name from list_instruments). Default: the `default` instrument, or the only one configured
`center_step_hz`	No	Center frequency step in Hz (> 0); turns the automatic step off
`center_step_auto`	No	Automatic center frequency step on/off

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 13, 2026

TDQS

A4.1/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 goes further by disclosing that frequency parameters are coupled, that settings are re-read afterwards, and that instrument-adjusted values surface in 'warnings'. That is exactly the kind of side-effect context annotations cannot convey. It does not say what happens when conflicting combinations 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 unit convention and the combination rules, then the behavioral consequence. No filler and nothing repeated from the schema verbatim.

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 10-parameter, all-optional mutation tool with no output schema, the description covers units, valid combinations, and the post-write re-read/warnings behavior. The main remaining gap is error behavior for invalid combinations, which an agent must discover at call time.

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 per-parameter meaning is already documented and a 3 would be the baseline. The description adds value beyond the schema by explaining the allowed OR-groupings and which parameters compose with all groups, clarifying interaction semantics the schema only partially captures.

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 opens with a specific verb and resource ('Set frequency parameters (all in Hz)'), so the agent knows exactly what domain is being modified. It does not explicitly separate itself from siblings such as set_ad_frequency or set_frequency_counter, so it stops short of full sibling differentiation.

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?

It spells out the valid parameter groupings ('center and/or span, OR start and/or stop, OR full_span, OR zero_span') and notes that step and offset can combine with any group, which is real usage guidance. It stops short of saying when to prefer this tool over the related frequency siblings.

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

Deploy Server