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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

scpi_query

Read-only

Send a raw SCPI query ending in '?' to a UNI-T UTS spectrum analyzer and return its reply; use block mode for IEEE 488.2 binary block responses.

Instructions

Send one raw SCPI query (it must end in '?') to the analyzer and return the reply. Escape hatch for commands without a dedicated tool. Use reply='block' for IEEE 488.2 '#' binary block replies (returned as base64). Unsupported queries get no reply from the instrument and time out.

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": {
      "command": "<command>"
    },
    "name": "scpi_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
replyNoReply type: 'text' (default) or 'block' for a binary block
commandYesSCPI query, e.g. '*IDN?' or ':SWEep:POINts?'
instrumentNoWhich instrument to use (a name from list_instruments). Default: the `default` instrument, or the only one configured
timeout_msNoTimeout in milliseconds (default 5000 for text, 30000 for blocks)

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?

readOnlyHint=true is consistent with a query, and the description adds real behavioral context beyond annotations: 'reply=block' returns IEEE 488.2 '#' binary blocks as base64, and unsupported queries yield no reply and time out. That failure mode is exactly the kind of information annotations cannot convey. It stops short of describing text-reply format or whether multiple queries per call are rejected.

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?

Three tight sentences, front-loaded with the core action and constraint, then the escape-hatch rationale, then the block/timeout caveats. No filler and nothing repeated from the schema.

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 output schema, the description carries the return-value burden and does so for the block case (base64) and the timeout case. What a text reply looks like (raw string) is only implied, so it is slightly short of fully complete for a query tool.

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, but the description earns more by explaining that 'block' replies come back base64-encoded, which clarifies the meaning of the reply enum beyond the schema's 'binary block' wording. Timeout defaults are left to the schema, which already documents them.

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 ('Send one raw SCPI query to the analyzer and return the reply') and pins the syntactic constraint ('must end in ?'). The framing as an 'escape hatch for commands without a dedicated tool' distinguishes it from the sibling scpi_command without needing to open either schema.

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 a clear selection rule: use this when no dedicated tool exists, plus the '?' requirement that separates queries from command writes. It does not explicitly name scpi_command as the alternative for non-query writes, so the routing is implied rather than spelled out.

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