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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

single_sweep

Switches the spectrum analyzer to single-sweep mode, runs exactly one sweep, and waits for completion so the trace is final and readable. Use continuous acquisition to resume normal sweeping.

Instructions

Switch to single sweep mode, run exactly one sweep and wait until it is complete, so the trace is final and can be read. Leaves the instrument in single mode; use set_acquisition continuous=true to resume normal sweeping.

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

Input Schema

NameRequiredDescriptionDefault
timeout_sNoGive up after this many seconds (default: sweep time + 10 s)
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.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description carries most of the burden and does well: it discloses the blocking wait, the persistent side effect ('leaves the instrument in single mode'), and how to undo that state. It does not say what happens if the timeout expires (error vs. partial trace), which is the main remaining behavioral gap.

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

Conciseness5/5

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

Two sentences, no filler, with the primary action and its outcome front-loaded and the state side effect plus remedy placed after. Every clause carries information.

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 tool with no output schema and minimal annotations, the definition covers purpose, blocking behavior, and mode side effects. Only the timeout failure semantics and the hint about reading the trace afterward (presumably via get_sweep) are left implicit.

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 timeout_s and instrument are already documented with defaults. The description adds only the indirect hint that waiting is bounded, but no extra semantics for either parameter. Baseline 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 ('run exactly one sweep and wait until it is complete') plus the resulting condition ('trace is final and can be read'). This clearly distinguishes the composite atomic operation from siblings like start_sweep and wait_for_sweep_complete.

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 a clear use condition (you need a final, readable trace) and explicitly names the exit path: 'use set_acquisition continuous=true to resume normal sweeping.' It does not explicitly say to prefer this over calling start_sweep plus wait_for_sweep_complete, but the phrasing implies the combined behavior.

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