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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_demod_result

Read-only

Retrieves analog demodulation numeric results—center frequency, carrier power/error, modulation rate, SINAD, distortion, THD, and RMS/peak values—from the active AD module without a screenshot.

Instructions

Get the AD (analog demodulation) module's numeric result window — center frequency, carrier power, carrier frequency error, modulation rate, SINAD, distortion/total Vrms, THD, and peak+/peak-/(pk-pk)/2/RMS for both the current and max-hold rows — without a screenshot. Wraps the undocumented bare :FETCh:AM?/:FETCh:FM? query (suffix 1, the default), confirmed live on this firmware (docs/verified-hardware.md). The AM/FM type is read fresh from :CONFigure? each call. AD module must be active (enter_analog_demod/select_instrument_module). This does not expose the RF spectrum trace, demodulated waveform or AF spectrum views (other FETCh suffixes); those remain screenshot-only. Units beyond what the live example confirmed (Hz, dB) are plausible, not independently verified.

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

Input Schema

NameRequiredDescriptionDefault
instrumentNoWhich 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.

  1. First observedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that it wraps an undocumented bare `:FETCh:AM?`/`:FETCh:FM?` query, that suffix 1 is the default, that the AM/FM type is read fresh from `:CONFigure?` each call, and that the query was confirmed on this firmware. It also documents the active-module requirement, the excluded views, and the uncertainty around units beyond Hz and dB.

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?

The description is dense but front-loads the core result and then adds only necessary caveats about query behavior, prerequisites, exclusions, and unit uncertainty. It is longer than typical because of the hardware-specific details, but most sentences earn their place; the field enumeration and parenthetical notes make it slightly heavy.

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 burden of explaining return values and does so by enumerating the numeric fields and the current/max-hold rows. It also covers prerequisites, exclusions, and the limits of verification, which is complete for a read-only hardware query tool.

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 only one parameter, and the schema fully documents that it selects the instrument by name from list_instruments, with a default. The description does not add further meaning beyond the schema, so the high schema coverage justifies a baseline score rather than extra credit.

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?

The description states a specific verb and resource: getting the AD module's numeric result window, then enumerates the exact measurements included. It also explicitly distinguishes this from the RF spectrum trace, demodulated waveform, and AF spectrum views, so an agent can tell it apart from screenshot-based alternatives.

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?

It states the prerequisite that the AD module must be active and names enter_analog_demod/select_instrument_module as the setup tools. It also explicitly says the RF spectrum trace, demodulated waveform, and AF spectrum views are not exposed here and remain screenshot-only, giving clear when-to-use and when-not-to-use guidance.

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