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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_amplitude

Read-only

Retrieve a spectrum analyzer's amplitude configuration, including reference level, power unit, scale, attenuation, preamp state, and input impedance.

Instructions

Get the analyzer's amplitude settings: reference level (in the current power unit), power unit, scale per division (dB), Y scale type, reference level offset (dB), input attenuation (dB) and whether it is automatic, preamp state and input impedance (ohms).

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_amplitude"
  }
}

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
Behavior4/5

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

readOnlyHint=true already establishes the safety profile, so the description's main added value is the detailed list of returned state, which matters because there is no output schema. It stops short of noting behavior such as what happens if no instrument is connected or whether values are cached versus read live.

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?

One front-loaded sentence — the verb and resource come first, then the field list. The enumeration is long but every item is load-bearing, effectively substituting for a missing output schema, so nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter read tool with no output schema, the description is complete enough to call correctly: it names the return contents exhaustively and the instrument parameter is covered by the schema. Nothing an agent needs 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 single instrument parameter is fully documented there (a name from list_instruments, with default behavior described), so the description legitimately does not restate it. Baseline 3 applies since the description adds no meaning beyond the schema for the only parameter.

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 ("Get the analyzer's amplitude settings") and then enumerates exactly which amplitude fields are returned — reference level, power unit, scale per division, Y scale type, reference level offset, attenuation, preamp, input impedance. That enumeration cleanly separates it from get_frequency, get_sweep, and the other get_* siblings.

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?

No explicit when-to-use statement, no mention of set_amplitude as the counterpart, and no prerequisites. Usage is only implied by the naming contrast between get_* and set_amplitude; the parenthetical "in the current power unit" hints that the tool reports live instrument state, but an agent gets no stated condition for choosing this over other getters.

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