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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_acquisition

Idempotent

Switch a spectrum analyzer between continuous and single sweep modes; in single mode, sweeps occur only when start_sweep or single_sweep is called.

Instructions

Switch between continuous sweep (continuous=true, the instrument's normal state) and single sweep mode (continuous=false, :INITiate:CONTINUOUS OFF). In single mode the instrument sweeps only when start_sweep or single_sweep is used.

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": {
      "continuous": "<continuous>"
    },
    "name": "set_acquisition"
  }
}

Input Schema

NameRequiredDescriptionDefault
continuousYestrue = continuous sweep, false = single sweep
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.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and idempotentHint=true; the description adds substantive context beyond that: the instrument's normal state is continuous, setting false issues :INITiate:CONTINUOUS OFF, and the consequence is that sweeps become trigger-driven. It does not mention whether the change persists across sessions or affects in-flight sweeps, but the core state semantics are covered.

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 tight sentences with the mode mapping front-loaded and the operational consequence second. No filler, no restatement of the tool name.

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 state-setting tool with no output schema, the description covers both modes, the default state, and the interaction with the sweep-trigger tools, which is what an agent needs to avoid a silent no-sweep surprise. Persistence of the setting and any error behavior on unsupported instruments are the only notable omissions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description adds value by identifying continuous=true as the instrument's normal/default state and tying continuous=false to a specific SCPI command, which the schema alone does not convey. The instrument parameter is left to the schema, which already documents its default, so no gap results.

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 ('Switch') plus the exact resource (acquisition sweep mode) and enumerates both states with their parameter values and the underlying SCPI command. It also implicitly distinguishes itself from the trigger tools by naming start_sweep and single_sweep as the way sweeps happen in single mode.

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 clear context for the two modes and explicitly tells the agent that in single mode it must use start_sweep or single_sweep to actually sweep, which is the key behavioral precondition. It stops short of an explicit 'use this when...' rule, but the mode semantics make the choice self-evident.

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