uni-t-uts-mcp

connect

Establishes a link to a UNI-T UTS spectrum analyzer over auto, VXI-11, or raw SCPI/TCP, returning identification and transport; use auto to discover one analyzer on the local network.

Instructions

Connect to a UNI-T UTS series spectrum analyzer over auto (default: VXI-11 when the instrument offers it, else raw SCPI/TCP), VXI-11 or raw SCPI/TCP. Returns the instrument identification and the transport in use. Use host "auto" (or UTS_IP=auto) to find the analyzer on the local network when exactly one answers. Using the analyzer puts it in remote mode and locks its front panel until Esc is pressed on the analyzer.

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

Input Schema

Name	Required	Description
`host`	No	Hostname or IP address of the analyzer (defaults to the UTS_IP env var); "auto" discovers it on the local network (see discover_instruments)
`name`	No	Instrument name (1-32 letters, digits, '_' or '-'). Default: the `default` instrument, or the only one configured. See list_instruments. connect creates the name when it is new (host and port then come from the arguments or UTS_INSTRUMENTS)
`port`	No	TCP port of the raw transport (defaults to the UTS_PORT env var, then 5025); VXI-11 finds its own port through the portmapper on port 111
`transport`	No	raw, vxi11 or auto (defaults to the UTS_TRANSPORT env var, then auto; raw when only a port is given). The VXI-11 device name comes from UTS_VXI11_DEVICE (default inst0)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only mark it non-read-only and open-world; the description adds the important side effect that connecting puts the analyzer in remote mode and locks the front panel until Esc, plus what the call returns. It also clarifies transport negotiation and fallback, which is behavior beyond the annotations.

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?

Four sentences, front-loaded with purpose and return value, then discovery and side effect. The parenthetical transport explanation is dense but every sentence carries necessary operational information without filler.

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 moderate-complexity connection tool with no output schema, it discloses the return values, transport defaults, discovery behavior, and the remote-mode side effect. It could be more complete about failure cases when auto finds zero or multiple instruments, but the core call requirements are covered.

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 the baseline is 3; the description adds useful meaning by specifying auto transport fallback to VXI-11 when offered and otherwise raw SCPI/TCP, and by noting host='auto' discovery. Most remaining parameter detail, such as environment variables and name creation, is already in the schema.

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 ('Connect') and resource ('UNI-T UTS series spectrum analyzer') plus supported transports, and immediately says it returns identification and transport. This distinguishes it from discovery and session-management tools well enough for selection.

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?

Explains auto transport defaulting and the host='auto' discovery condition ('when exactly one answers'), giving clear context for the common setup path. It does not explicitly say when to prefer discover_instruments/list_instruments or when not to call connect, so it stops short of full alternative routing.

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

Deploy Server