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

uni-t-uts-mcp

by Reid-n0rc

set_emi_peak_criteria

Idempotent

Configure EMI peak search criteria on a UNI-T UTS spectrum analyzer by setting the peak threshold or excursion, or switch either criterion back to automatic mode.

Instructions

Set the EMI peak search criteria. Giving threshold_dbm or excursion_db turns that criterion's automatic mode off; threshold_auto / excursion_auto true switches it back to automatic. Values the instrument changed are reported in 'warnings'.

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

Input Schema

NameRequiredDescriptionDefault
instrumentNoWhich instrument to use (a name from list_instruments). Default: the `default` instrument, or the only one configured
excursion_dbNoPeak excursion in dB, 0 to 100; a peak must rise this far above the valleys beside it
threshold_dbmNoPeak threshold in dBm, -200 to 30; a peak must be above it
excursion_autoNoAutomatic excursion on/off (not true together with excursion_db)
threshold_autoNoAutomatic threshold on/off (not true together with threshold_dbm)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and idempotentHint=true; the description adds real behavioral detail beyond that, namely the coupling between value parameters and the corresponding auto flags (setting threshold_dbm silently disables threshold_auto) and the fact that instrument-side adjustments surface in a 'warnings' field. It does not describe error behavior or whether unchanged criteria are re-sent, so not a 5.

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 clauses with the tool's action front-loaded, then the mutual-exclusion rule, then the return side-effect. No filler and no repetition of schema-documented ranges.

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 5-parameter mutation tool with no output schema, the description covers the essential state-machine behavior and where changed values are surfaced. Missing only failure modes (what happens if both auto=true and a value are supplied) which would make it fully self-sufficient.

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%, and the schema itself already documents ranges and the 'not true together with' exclusivity, so the schema does most of the work. The description adds the directional rule (a value turns auto off; auto=true turns it back on), which is genuinely beyond the schema, but it adds nothing about the instrument parameter.

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 and resource: 'Set the EMI peak search criteria', which cleanly separates it from set_peak_criteria and from the read-only get_emi_peak_criteria sibling. It does not explicitly name an alternative, but the EMI qualifier does the disambiguating work.

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 through the semantics of the criteria rather than stated: the description explains that supplying a value forces manual mode, which tells the agent how to use the parameters, but never says when to choose this tool over a sibling get/set variant or what preconditions exist.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.