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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

emi_stop

Stops a running EMI scan sequence on a UNI-T UTS spectrum analyzer by sending :INITiate:STOP and reports if the instrument returns an error.

Instructions

Stop a running EMI scan sequence (:INITiate:STOP). Live-verified 2026-11-12: accepted without an instrument error in EMI mode (unlike SA, where this command gives -113). No independent confirmation that it actually halted anything was taken (no documented read-back); the result only reports whether the instrument raised an error.

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

Input Schema

NameRequiredDescriptionDefault
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.1/5.0
Behavior5/5

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

Beyond the single readOnlyHint=false annotation, the description discloses the mode-specific acceptance behavior (-113 in SA mode), the negative verification result (no read-back, so no confirmation the scan actually halted), and what the response conveys (only whether the instrument raised an error). That is unusually candid disclosure of an operational limitation and is consistent with the non-read-only annotation.

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 purpose is front-loaded in the first clause, followed by compact verification notes. The dated verification caveat is slightly verbose but earns its place because it changes how an agent should interpret success.

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 single-optional-parameter tool with no output schema, the description covers the essential gap: what the result actually means (only error status, not proof of halt). Nothing critical is missing, though a pointer back to emi_run for restarting would round it out.

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?

There is one optional parameter with 100% schema coverage, and the schema already documents the default fallback (the `default` instrument or the only configured one). The description adds no further meaning about the instrument parameter, which is acceptable given the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Stop a running EMI scan sequence") and names the underlying SCPI command, so the agent knows exactly what operation this performs. It is clearly the counterpart to emi_run, though it never explicitly names that sibling to complete the differentiation.

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?

Usage context is clear: this is for halting an in-progress EMI scan, and the note that it is accepted in EMI mode but yields -113 in SA mode tells the agent when this call is valid versus not. It stops short of naming the alternative tool to start a scan, so routing guidance is implied rather than explicit.

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