uni-t-uts-mcp

get_frequency

Read-only

Retrieve a UNI-T spectrum analyzer’s frequency settings—center, span, start, stop, center step with auto status, and offset—all in Hz to verify or adjust sweep ranges.

Instructions

Get the analyzer's frequency settings: center, span, start, stop, center step (and whether it is automatic) and offset, all in Hz.

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": "get_frequency"
  }
}

Input Schema

Name	Required	Description	Default
`instrument`	No	Which instrument to use (a name from list_instruments). Default: the `default` instrument, or the only one configured

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?

readOnlyHint=true already establishes the safety profile, so the description's added value is elsewhere: it names the exact quantities returned, discloses units (Hz) for every value, and calls out that center step carries an automatic flag. That is meaningful disclosure beyond the annotations and matters because no output schema exists.

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?

One front-loaded sentence with the resource first and the returned fields enumerated, ending in a single global unit qualifier that avoids repeating 'in Hz' per field. No filler.

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 read-only getter with one optional, fully documented parameter and no output schema, the description supplies the key missing piece by listing returned values and their units. Only the instrument-scoping behavior is left entirely to the schema, which is acceptable given its full coverage.

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?

The single 'instrument' parameter has 100% schema description coverage, including the default-instrument fallback, so the schema carries the semantics. The description says nothing about parameterizing by instrument, leaving it at the baseline for high coverage.

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 and resource ('Get the analyzer's frequency settings') and enumerates exactly which settings are returned (center, span, start, stop, center step with auto flag, offset). An agent can distinguish it from set_frequency and get_frequency_counter by the field list, though no sibling is named explicitly.

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 only implied by the read verb 'Get' and the settings-oriented field list; there is no explicit statement of when to call this versus set_frequency or the other get_* settings tools. Adequate to infer intent, but no routing guidance is provided.

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

Deploy Server