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

uni-t-uts-mcp

by Reid-n0rc

get_peak_criteria

Read-only

Reads the peak search criteria — threshold in dBm and excursion in dB — including each automatic flag, so you can see whether the analyzer derives values from the trace.

Instructions

Read the peak search criteria: threshold (dBm) and excursion (dB), each with its automatic flag. In automatic mode the instrument derives the value from the trace.

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

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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful context: what the criteria consist of, their units, and the semantics of automatic mode ('the instrument derives the value from the trace'), which tells the agent what the automatic flag actually implies.

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?

Two sentences, front-loaded with what is read and which fields it returns, followed by the one piece of non-obvious semantics the agent needs. No filler.

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 small read tool with a fully documented single parameter and readOnly annotations, the definition is essentially complete; it even explains what comes back (threshold, excursion, flags) despite there being no output schema. Minor omission is any hint about the manual vs. automatic distinction's effect on the returned flag values.

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?

The single 'instrument' parameter is fully documented in the schema at 100% coverage. The description says nothing additional about it, so the schema does all the work and the baseline 3 applies.

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 'Read' and resource 'peak search criteria', then enumerates the fields (threshold in dBm, excursion in dB, automatic flags). The operation is unmistakable. It does not, however, explicitly differentiate itself from set_peak_criteria or get_emi_peak_criteria, leaving the sibling distinction to be inferred from the name.

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?

'Read' implies inspection but there is no explicit statement of when to prefer this over set_peak_criteria (mutation) or get_emi_peak_criteria (EMI variant). No prerequisites or exclusions are given, so the agent must infer selection from sibling names alone.

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