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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

restart_trace

Restart a trace's max hold, min hold, or averaging accumulation by re-sending its current trace type; omit trace to reset every hold/average trace.

Instructions

Restart max hold, min hold or averaging by re-sending the trace's current type (:TRACe:TYPE ). Verified on the instrument: this clears the accumulated hold/average and starts over, and so do changing the type or the update state; :INITiate:RESTart and :INITiate:IMMediate do NOT. Without trace every trace that is in average, max_hold or min_hold is restarted; write traces need no restart.

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": "restart_trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
traceNoOnly this trace (1-6); every hold/average trace when omitted
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.1/5.0
Behavior5/5

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

Goes well beyond readOnlyHint=false: it names exactly what data is destroyed (accumulated hold/average), confirms instrument-verified behavior, and rules out two plausible but non-working alternatives (:INITiate:RESTart, :INITiate:IMMediate). The destructive nature implied by the annotation is consistent with clearing accumulated data, so there is no contradiction.

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?

Front-loads the action and mechanism in the first clause, then layers scope and verification detail. Information-dense with little waste, though the parenthetical SCPI re-send and the :INITiate caveats make it longer than strictly necessary for a simple restart call.

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?

A mutation tool with no output schema and no required parameters; the description covers the affected state, default scope, and safety-relevant effects thoroughly. It does not describe return values or error behavior on an invalid trace number, a minor gap given there is no output schema.

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% and the schema already documents both `trace` (1-6, all hold/average traces when omitted) and `instrument`. The description restates the omit-behavior but adds no format or syntax detail beyond the schema, so baseline 3 is appropriate.

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 (Restart) plus the exact resources affected (max hold, min hold, averaging) and even discloses the mechanism (:TRACe<n>:TYPE). It is clear what the tool does, though it does not explicitly name a sibling (e.g., set_trace) as the alternative for changing type.

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?

Gives concrete when-to-use scope: only traces in average/max_hold/min_hold need restarting, and 'write traces need no restart.' It also warns that changing type or update state accomplishes the same thing, and that :INITiate:RESTart/:INITiate:IMMediate do not, which steers the agent away from wrong commands. No explicit named-tool alternative is offered, keeping it at 4.

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