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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_marker_function

Idempotent

Configure a spectrum analyzer marker to measure noise level, band power, band density, or turn it off, and set the band span for power or density readings.

Instructions

Set a marker's function: noise (noise level per Hz), band_power (power in the band), band_density (power density in the band) or off. band_span_hz sets the band width for band_power and band_density. Read the result with get_marker. Values the instrument changed are reported in 'warnings'.

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>"
    },
    "name": "set_marker_function"
  }
}

Input Schema

NameRequiredDescriptionDefault
markerYesMarker number, 1 to 10
functionNoMarker function
instrumentNoWhich instrument to use (a name from list_instruments). Default: the `default` instrument, or the only one configured
band_span_hzNoBand span in Hz for band_power / band_density

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, so the mutation profile is covered. The description adds genuinely non-structured behavior: the instrument may clamp or adjust values, and any such changes are surfaced in a 'warnings' field — important for an agent deciding whether the set actually took effect as requested.

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, front-loaded with the operation and its mode enum, followed by the conditional parameter note and the read-back hint. No filler, though the 'warnings' sentence is appended somewhat abruptly.

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 four-parameter setter with full schema coverage, annotations, and no output schema, the description covers the operation, the mode semantics, the band-width coupling, how to verify results, and the warning channel. Only the instrument selection/default behavior and error handling for invalid marker or mode combinations are left implicit.

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%, so all four parameters (marker, function, instrument, band_span_hz) are already documented with constraints and enums. The description's band_span_hz note largely restates the schema text, and the instrument parameter and its default resolution are not discussed at all, so it adds little beyond the structured data.

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?

"Set a marker's function" names a specific verb and resource, and the four allowed modes (noise, band_power, band_density, off) are enumerated, so an agent knows exactly what the call changes. It does not explicitly separate itself from the read-side siblings get_marker_function or the other marker setters, which keeps it short of a 5.

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?

The description gives partial routing: it says band_span_hz is required context only for band_power and band_density, and that results are read back with get_marker. It never states when to pick band_power over band_density versus noise, or when this tool is preferable to related marker tools; usage is implied rather than prescribed.

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