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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_sweep

Read-only

Retrieve spectrum analyzer sweep settings, including sweep time and auto rules, sweep type, trace points, trigger source, and video trigger level for configuration checks.

Instructions

Get sweep settings: sweep time (s) with auto flag and auto rule, sweep type (sweep/fft) with auto flag, sweep points (the trace length), trigger source (immediate/video) and video trigger level (dBm).

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

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

B3.2/5.0
Behavior3/5

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

The readOnlyHint annotation already covers the safety profile, and the description adds useful substance by listing the exact settings and their units (seconds, dBm) plus enumerated values for sweep type and trigger source. However, it does not describe the shape of the returned object or how auto flags interact with auto rules, leaving behavioral disclosure incomplete beyond the field list.

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?

One front-loaded sentence enumerates all returned fields without filler. The parenthetical units and option lists are dense but each earns its place; slight density in the middle clause is the only structural weakness.

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 appropriately enumerates the return values and their units, which is the key information an agent needs for a simple getter. It could say more about return structure or the auto-rule semantics, but it is substantially complete for this tool's complexity.

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 coverage is 100%, so the single optional `instrument` parameter is fully documented in the schema itself. The description adds no parameter-level meaning, which is acceptable at this coverage level.

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?

States a specific verb+resource ('Get sweep settings') and enumerates exactly which settings are returned (sweep time, sweep type, sweep points, trigger source, video trigger level). This clearly distinguishes it from data-returning siblings like get_trace_data, though it does not explicitly name its write counterpart set_sweep.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no mention of when to prefer set_sweep for modification, and no prerequisites or context about when sweep settings are relevant. Usage is only implied by the verb 'Get'.

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