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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_detector

Idempotent

Configures the detector mode or automatic detector selection for a selected trace (1–6) on a UNI-T UTS spectrum analyzer, including sample, positive, negative, normal, and average modes.

Instructions

Set the detector of one trace (1-6): sample, positive, negative, normal or average (turns that trace's automatic detector off), or switch automatic selection on/off.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "trace": "<trace>"
    },
    "name": "set_detector"
  }
}

Input Schema

NameRequiredDescriptionDefault
autoNoAutomatic detector selection for the trace; not with detector=...
traceYesTrace number 1-6
detectorNoDetector mode
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

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true), the description discloses a real side effect: selecting a detector mode turns that trace's automatic detector off. That is meaningful behavioral context for a mutating tool. It still omits confirmation/return behavior and permission requirements, keeping it short of a 5.

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?

One front-loaded sentence that opens with the verb and resource and wastes no words. The nested parenthetical for the five modes is slightly hard to parse, and it is unclear whether '(turns that trace's automatic detector off)' applies to all modes or only to 'average'.

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 four-parameter, fully schema-documented setter with no output schema, the definition covers purpose, scope, and the key side effect. The main residual gaps are the detector/auto exclusivity framing and the untouched 'instrument' parameter, both of which the schema already carries.

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 description coverage is 100%, so all four parameters are already documented, making 3 the baseline. The description adds a little meaning by framing 'auto' as switching automatic selection on/off and by noting the effect of choosing a mode, but the enum listing largely duplicates the schema and the parenthetical's scope is ambiguous.

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 gives a specific verb and resource ('Set the detector of one trace') and scopes it to traces 1-6, so it is clearly distinct from the sibling get_detector. It enumerates the available modes, which makes the operation concrete, though it does not explicitly name a sibling alternative for reading the current detector.

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?

Usage is only implied: the sentence presents two paths ('set the detector...' or 'switch automatic selection on/off'), which hints at the detector-vs-auto choice. It never states when to pick this tool over get_detector, nor does it state the exclusion rule between 'detector' and 'auto' as guidance (that constraint lives only in the schema description for 'auto').

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