uni-t-uts-mcp

get_detector

Read-only

Retrieve the detector type (sample, positive, negative, normal, average) and auto flag for one trace or all six on a UNI-T UTS spectrum analyzer.

Instructions

Get the detector (sample, positive, negative, normal, average) and its auto flag for one trace (1-6) or all six, via :SENSe:DETector:TRACe.

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

Input Schema

Name	Required	Description	Default
`trace`	No	Trace number 1-6; all traces 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.6/5.0

Behavior4/5

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

readOnlyHint=true already establishes the safety profile, so the description's added value is the disclosure of what is actually returned — the detector mode and its auto flag — which matters because there is no output schema. The SCPI command reference (:SENSe:DETector:TRACe<n>) also anchors the behavior to a known instrument operation. It stops short of noting error behavior for an invalid trace or an unconfigured instrument.

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 with no filler; the parenthetical value list and SCPI path both carry information. It is dense but readable, with only mild redundancy between 'one trace (1-6) or all six' and the schema's own wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 getter with no output schema, the description covers the return contents and trace scoping adequately. What is missing is how the 'auto' flag relates to set_detector (i.e., whether a manual set clears auto), which an agent would need to interpret the result correctly.

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 (trace, instrument) are already documented, including the 1-6 range and the 'all traces when omitted' default. The description restates the trace range and 'all six' semantics without adding format or edge-case detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ('Get the detector') and enumerates the possible detector modes (sample, positive, negative, normal, average) plus the auto flag, so the agent knows exactly what comes back. The get/set pairing with set_detector is implied by the verb but never explicitly contrasted.

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 scoping phrase 'for one trace (1-6) or all six' tells the agent how to use the parameter, which is real usage guidance. It never states when to prefer this over alternatives such as get_trace or get_trace_data, nor any prerequisites (e.g., which instrument/module must be active).

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

Deploy Server