uni-t-uts-mcp

get_trace

Read-only

Retrieve the selected trace and per-trace settings—type, live/hold update, display state—plus global average count and type for UNI-T UTS spectrum analyzers.

Instructions

Get the trace configuration: the selected (current) trace, and for each trace 1-6 (or only trace) its type (write, average, max_hold, min_hold), update state (true = live, false = view/hold) and display state, plus the global average count and average type. Trace math cannot be read (the instrument has no query for it).

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

Input Schema

Name	Required	Description	Default
`trace`	No	Only this trace (1-6); all six when omitted
`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.9/5.0

Behavior4/5

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

Consistent with readOnlyHint=true. Beyond the annotation it discloses the field-level return contents (types, update vs display state, global average settings) and a genuinely useful negative capability: trace math has no query, so an agent won't waste calls attempting it.

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?

A single front-loaded sentence that gets to the resource immediately, followed by the limitation. The nested parentheticals make it dense, but no sentence is wasted and the ordering is sensible.

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?

With no output schema, the description carries the return-value burden and mostly discharges it by naming every returned field group. Minor gaps remain: no mention of what an unconfigured or held trace presents in the response, or whether the call can fail for an out-of-range trace.

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?

Schema coverage is 100%, so both parameters are already documented, including the 1-6 range for `trace` and the `instrument` name lookup. The description restates the '1-6 or only trace' scoping without adding format or behavioral detail, so the baseline of 3 applies.

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?

States a specific verb and resource (get the trace configuration) and then enumerates exactly what is returned: selected trace, per-trace type (write/average/max_hold/min_hold), update state, display state, global average count and type. The scope is unmistakably configuration state rather than measurement data, which separates it from get_trace_data.

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?

The purpose implies when to use it (inspecting how traces are configured), and the closing note that trace math cannot be read implies a boundary. However, no sibling is named and there is no explicit when-to-use/when-not guidance or pointer for reading trace math through another means.

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

Deploy Server