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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ad_markers_all_off

Idempotent

Turns off all six AD markers on the active demod type and confirms each marker's mode, verifying they are disabled. Requires the AD module to be active.

Instructions

Turn every AD marker off (:CALCulate:AM|FM:MARKer:AOFF for the current demod type) and confirm it by reading each of the six markers' mode. AD module must be active. Live-verified (2026-11-12).

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": "ad_markers_all_off"
  }
}

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

A4.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and idempotentHint=true, and the description is consistent with both while adding value: it discloses the post-condition verification step (reading back all six markers' modes) and the AD-module prerequisite. It does not spell out failure behavior when the module is inactive, but it goes well beyond the annotations.

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?

One compact sentence with the action front-loaded, followed by the verification behavior and the precondition. Every clause carries information; the parenthetical SCPI detail is slightly technical but earns its place for precise identification.

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 zero-required-parameter mutation with no output schema, the definition covers what it does, what it verifies afterward, and the module prerequisite. Minor omission: it does not state what happens if the AD module is not active (error vs no-op) or what the confirmation read returns.

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?

There is a single optional parameter with 100% schema description coverage, so the schema already explains the 'instrument' argument. The description adds nothing about instrument resolution, which is acceptable at full coverage — baseline 3.

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 names a specific verb and resource ('Turn every AD marker off'), scopes it to the current demod type, and even cites the underlying SCPI command (:CALCulate:AM|FM:MARKer:AOFF). The 'AD' qualifier plus the 'current demod type' phrasing distinguishes it from generic or EMI marker siblings.

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 states a hard precondition — the AD module must be active — which tells the agent when the call is valid, and the scope ('current demod type') clarifies which markers are affected. It stops short of explicitly routing the agent elsewhere (e.g., EMI marker equivalents), so it is clear context without exclusions.

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