uni-t-uts-mcp

get_ad_settings

Read-only

Retrieve a read-only snapshot of an active analog demodulation module’s demodulation type, center frequency, RF span, bandwidth, timing, averaging, and input impedance settings.

Instructions

Get a read-only snapshot of the AD (analog demodulation) module's frequency, bandwidth and demod-timing settings: current demodulation type (AM/FM, via :CONFigure?), center frequency and step, RF span and resolution bandwidth, demodulation bandwidth, AF spectrum start/stop and bandwidth, demod window sweep time, demod time and averaging, and input impedance. AD module must be active (enter_analog_demod/select_instrument_module). Filters, audio and display/marker settings are not included here (separate tool groups). A silent or malformed reply to any query is an error naming that command; no partial snapshot is ever returned. :CONFigure? and most of these getters are not yet live-verified on this firmware (docs/verified-hardware.md); treat results as plausible, not confirmed.

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_ad_settings"
  }
}

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

A4.4/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=true, and the description adds substantial behavior: failure is atomic ("no partial snapshot is ever returned"), errors name the failing command, and reliability is flagged (:CONFigure? and most getters are "not yet live-verified on this firmware ... treat results as plausible, not confirmed"). Those are exactly the caveats an agent needs and none are available in structured fields.

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?

Purpose and scope are front-loaded, followed by prerequisites, exclusions, error semantics and the verification caveat in a logical order. The long mid-sentence enumeration of getters is dense but each item conveys what the snapshot contains; only that list could be tightened.

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?

With no output schema, the description carries the return-value burden and does so by listing the covered settings group by group. Combined with the active-module prerequisite, the no-partial-result guarantee and the firmware verification warning, an agent has everything needed to call this and interpret the result.

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?

There is a single optional `instrument` parameter with 100% schema description coverage, so the schema already explains it (a name from list_instruments, with default behavior). The description adds nothing about parameter selection, which is acceptable at full coverage and matches the baseline.

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?

Names a concrete verb and resource ("Get a read-only snapshot of the AD module's frequency, bandwidth and demod-timing settings") and then enumerates the specific fields returned. It also draws an explicit boundary against sibling groups: "Filters, audio and display/marker settings are not included here (separate tool groups)," which separates it from set_ad_filters, set_ad_audio and get_ad_marker.

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?

States the precondition plainly: "AD module must be active (enter_analog_demod/select_instrument_module)," routing the agent to the right setup siblings. It also says which settings are out of scope and belong to other tool groups. There is no explicit when-not-to-use beyond that, so it falls short of a full 5.

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

Deploy Server