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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_measurement

Read-only

Check if a UNI-T UTS analyzer is in spectrum analyzer mode, or verify a named measurement and return its parameters.

Instructions

Report whether the instrument is in spectrum analyzer mode, or check one measurement. The instrument has no query for the active measurement, so without 'measurement' this asks one query that only spectrum analyzer mode answers (spectrum_analyzer, or an error that a measurement is active). With 'measurement' (channel_power, time_power, obw, acpr, toi, cn or harmonics) it checks that measurement and returns its parameters; an error means it is not active. A check that gets no reply costs a few seconds while the instrument recovers.

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

Input Schema

NameRequiredDescriptionDefault
instrumentNoWhich instrument to use (a name from list_instruments). Default: the `default` instrument, or the only one configured
measurementNoCheck this measurement and return its parameters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds real behavioral context: there is no query for the active measurement, an error response means the measurement is not active, and a check that receives no reply costs a few seconds while the instrument recovers. That timeout and error semantics go well beyond the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first clause is front-loaded and efficient, but the middle sentence is a dense, hard-to-parse run-on about the missing active-measurement query. The content is useful, yet the structure could be broken up and tightened.

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 two-parameter, read-only probe with no output schema, the definition covers what each mode returns (spectrum_analyzer, the measurement's parameters, or an error) and the timeout risk. It is nearly complete, lacking only a pointer to the sibling tools that configure or read measurements.

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 the baseline would be 3, but the description adds meaning the schema does not: omitting 'measurement' triggers a different query path, and supplying it returns that measurement's parameters or an error indicating it is not active. That explains what each parameter value actually does.

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 uses a specific verb and resource, stating that it reports whether the instrument is in spectrum analyzer mode or checks one named measurement, then enumerates the valid measurement values. The purpose is unambiguous, but it never names a sibling (for example configure_measurement or read_measurement), so the agent gets no explicit 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 clearly separates the two usage modes: omit 'measurement' to test spectrum analyzer mode, or supply 'measurement' to test a specific measurement. What is missing is guidance on when to call this instead of the sibling configuration or read tools, so exclusions are absent.

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