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

uni-t-uts-mcp

by Reid-n0rc

set_peak_criteria

Idempotent

Set peak search criteria on a spectrum analyzer by defining threshold and excursion values or switching either to automatic mode; changed values are returned in warnings.

Instructions

Set the peak search criteria. Giving threshold_dbm or excursion_db turns that criterion's automatic mode off (verified on the instrument); 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_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.7/5.0
Behavior3/5

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

With annotations already declaring the write (readOnlyHint=false) and idempotent nature, the description adds real value by disclosing that supplying a value silently disables that criterion's automatic mode and that *_auto=true re-enables it — a non-obvious side effect. It also mentions a 'warnings' channel for instrument-adjusted values, which matters since no output schema exists. The remaining gap is that it says nothing about persistence or whether the change survives a preset recall.

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?

Three tight sentences that front-load the purpose and then the mode-switching rule, with no filler. "(verified on the instrument)" is a slight aside but earns its place by signaling observed rather than assumed behavior.

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 five-parameter all-optional mutator with no output schema, the description covers the essential unknowns: the auto-mode side effect and the return of changed values under 'warnings'. Nothing an agent needs in order to call it correctly is missing.

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 all five parameters are already documented, and the description still contributes the cross-parameter interaction rule (value vs. auto flag) that the schema does not encode. That extra meaning pushes it above the baseline 3, short of 5 because units and ranges are fully left to the schema.

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 peak search criteria") that an agent can match to the peak-search domain. It does not, however, distinguish itself from the sibling read counterpart get_peak_criteria or from set_emi_peak_criteria, leaving the agent to infer the split from names alone.

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 only implied: the note about switching automatic mode off and back on amounts to mode-selection guidance for the two criteria. It never states when to call this rather than get_peak_criteria or set_emi_peak_criteria, and there are no preconditions or exclusions spelled out.

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