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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ad_marker_search

Moves an AD marker to a peak, next peak, minimum, or peak-to-peak search result on a UNI-T UTS spectrum analyzer and returns the marker's new state.

Instructions

Move an AD marker with a search and return its new state. AD module must be active. Actions: peak (highest), next_peak, next_left / next_right (next peak left/right of the marker), minimum, peak_to_peak (the marker becomes a delta marker). A search turns a marker that is off on. Live-verified (2026-11-12): peak search found a real external signal exactly.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "marker": "<marker>",
      "action": "<action>"
    },
    "name": "ad_marker_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesWhich search to run
markerYesMarker number, 1 to 6 (AD has six markers per demod type, not SA's ten)
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.3/5.0
Behavior4/5

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

Beyond the readOnlyHint=false annotation it discloses real side effects: a search turns an off marker on, and peak_to_peak converts the marker into a delta marker, i.e. it mutates marker state, not just position. It also says it returns the new state, though it does not describe the return shape and there is no output schema.

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?

Purpose is front-loaded, followed by the prerequisite and then the action glossary, so the important information comes first. The trailing 'Live-verified (2026-11-12)' note is a mild digression that could be trimmed without losing meaning.

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 three-parameter mutating tool with no output schema, the description covers purpose, precondition, per-action semantics, and state effects. The only gap is that the returned 'new state' is not characterised at all, which the absence of an output schema leaves unaddressed.

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 the baseline is 3, but the description earns extra by defining the enum values: peak is the highest peak, next_left/next_right are the next peak to either side of the marker, and peak_to_peak makes it a delta marker. The instrument parameter is left entirely to the schema.

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?

The description states a specific verb and resource — moving an AD marker by running a named search — and scopes it to the AD module, which distinguishes it from the SA-flavoured siblings such as marker_search and emi_marker_search without needing their schemas.

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

Usage Guidelines4/5

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

It gives a concrete prerequisite (the AD module must be active) and explains what each search action selects, which tells the agent when this tool is applicable. It stops short of explicitly routing to a specific alternative sibling, but the AD scoping makes the domain unambiguous.

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