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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

disconnect

Close the active connection to a specified or default spectrum analyzer while keeping the instrument registered for future reconnection.

Instructions

Disconnect from the spectrum analyzer (the instrument named by name, default: the default one). The name stays registered so it can be connected again.

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

Input Schema

NameRequiredDescriptionDefault
nameNoInstrument name (1-32 letters, digits, '_' or '-'). Default: the `default` instrument, or the only one configured. See list_instruments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior4/5

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

The `readOnlyHint: false` annotation already signals a state-changing call, and the description goes beyond it with the non-obvious fact that the instrument name stays registered after disconnection. It does not say what happens if the instrument is not currently connected (error vs. no-op) or whether in-flight operations are aborted.

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 short sentences with the action and target front-loaded, followed by the state consequence. No filler or redundant restatement of the title.

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 one-optional-parameter tool with no output schema, the description covers the action, target selection, and post-call state, which is nearly everything an agent needs. Only edge-case behavior for disconnecting an already-disconnected instrument is missing.

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 description coverage is 100% and the schema already documents the name format, the default instrument, and the pointer to list_instruments. The description only restates the default behavior, adding little meaning beyond the structured field.

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 ("Disconnect from the spectrum analyzer") and immediately clarifies which instrument via the `name` parameter and its default. An agent can distinguish this from the `connect` sibling without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the reconnect note ("so it can be connected again"), which signals the pairing with `connect`, but there is no explicit statement of when to call this versus leaving a session open, nor any preconditions such as requiring an existing connection.

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