uni-t-uts-mcp

list_instruments

Read-only

List known spectrum analyzers and show whether each is connected, its address and transport, and which instrument handles unnamed commands; read-only.

Instructions

List the instruments this server knows by name (the default one, those from UTS_INSTRUMENTS and any added with connect name=...): whether each is connected, where, over which transport, and which one is used when no name is given. Read-only; the serial number is not shown.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds real value beyond that: it discloses what each entry reports (connected state, location, transport, and which instrument is the default when no name is given) and explicitly notes the serial number is not exposed. The 'Read-only' restatement is redundant with the annotation, which keeps it from 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?

The scope constraint is front-loaded and the second sentence delivers the two most important caveats (read-only, serial hidden). It is a single dense sentence plus a fragment, with a parenthetical list that is slightly awkward but 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?

With no parameters and no output schema, the description has to carry the return-shape burden, and it does partially by naming the fields surfaced per instrument and flagging the omitted serial number. It stops short of describing ordering or entry format, which would be useful given the missing output schema.

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?

The tool takes zero parameters and the schema is empty, so there is nothing for the description to disambiguate. Baseline of 4 applies; the text adds nothing that would be needed for arguments because none exist.

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 ("List the instruments this server knows") and pins the exact scope: the default one, those from UTS_INSTRUMENTS, and any added with 'connect name=...'. An agent can immediately tell this apart from connect or discover_instruments because it enumerates the known-set rather than establishing or finding connections.

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?

The description gives clear context for when this is the right call: you want the roster of already-known instruments plus per-instrument status. It ties itself to 'connect name=...' so the agent understands the lifecycle relationship, but never explicitly states when not to use it or names discover_instruments/connect as the alternative for finding new hardware.

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

Deploy Server