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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_instrument_module

Read-only

Reads the active measurement module (spectrum analyzer, EMI, or analog demod) from a UNI-T UTS instrument, returning the current mode safely without changing settings.

Instructions

Get the active measurement function module: spectrum_analyzer, emi or analog_demod. Read-only, safe in any module. An unexpected reply (not SA/EMI/AD) is an error quoting it rather than a guess.

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

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.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, so the safety claim is partly redundant, but the description adds genuinely new behavior: it defines the success space (only SA/EMI/AD are valid) and prescribes error handling for unexpected replies — quote the value rather than guess. That is context the annotation cannot carry.

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 short sentences, front-loaded with the purpose and followed by the safety and error semantics. No filler, no restatement of the name.

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 simple no-argument getter with no output schema, the description supplies exactly the missing piece — the set of values that can come back and how to handle anything outside it — which is precisely what the absent output schema would otherwise have to convey.

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 parameter with 100% schema description coverage, so the schema already explains the instrument argument and its default. The description adds nothing about it; baseline 3 applies when the schema carries the full load.

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 specific verb and resource (the active measurement function module) and enumerates the exact possible values: spectrum_analyzer, emi, analog_demod. The word "active" distinguishes it from the setter sibling select_instrument_module, so an agent can tell get from set 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Read-only, safe in any module" gives a clear condition for calling it and reassures the agent that no module-specific preconditions apply. It stops short of explicitly naming select_instrument_module as the counterpart used to change the module, leaving that inference to the agent.

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