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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_marker_ndb

Idempotent

Enable or disable a marker’s N-dB bandwidth measurement and set the dB offset below the marker; returns the measured bandwidth in Hz or null while off.

Instructions

Turn a marker's N-dB bandwidth measurement on or off and/or set N (dB below the marker, -140 to -0.01, e.g. -3 or -6). Returns the state including the measured bandwidth in Hz (null while off).

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

Input Schema

NameRequiredDescriptionDefault
ndbNoN in dB, negative: -140 to -0.01
markerYesMarker number, 1 to 10
enabledNoTurn the N-dB measurement on or off
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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, so the bar is lower, and the description usefully adds the return contract ('state including the measured bandwidth in Hz, null while off'). However, it does not resolve the key behavioral ambiguity of the 'and/or' semantics — whether supplying ndb alone implicitly enables the measurement, or whether enabled must be set separately.

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?

Two sentences, front-loaded with the action and followed by the return contract; no filler. The parenthetical range/example is slightly redundant with the schema but does not bloat the text.

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?

With no output schema, the description correctly supplies the return shape and the off-state null behavior for a 4-parameter mutation tool. The only real gap is the interaction between ndb and enabled, which matters given the 'and/or' phrasing.

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 the baseline is 3. The description restates the ndb range already in the schema but does add gloss ('dB below the marker', e.g. -3 or -6) and clarifies that the returned bandwidth is null while off; it adds nothing for marker, enabled, or instrument beyond 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?

Names a specific verb and resource ('Turn a marker's N-dB bandwidth measurement on or off and/or set N') and states the returned value, so the operation is unambiguous. It never names the read counterpart get_marker_ndb explicitly, so sibling differentiation is only implied by the 'set/turn on-off' framing.

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 by the verb: use this when you need to enable, disable, or change the N-dB offset. There is no explicit when-to-use/when-not guidance and no reference to alternatives such as get_marker_ndb for reading state, leaving the agent to infer.

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