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

uni-t-uts-mcp

by Reid-n0rc

emi_markers_all_off

Idempotent

Turn off all EMI markers on a UNI-T UTS spectrum analyzer and verify each marker's mode to confirm the change.

Instructions

Turn every EMI marker off (:CALCulate:FSCan:MARKer:AOFF) and confirm it by reading each marker's mode.

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": "emi_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

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 state-changing and repeatable nature is covered structurally. The description adds genuine context beyond that: it is a bulk operation over every marker and it verifies the result by reading back each marker's mode, which tells the agent to expect read traffic and a verification step after the write.

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 front-loaded sentence states the action, the exact command, and the verification step with no filler. The inline SCPI token is slightly technical noise for an agent but it does reinforce exactly what is executed.

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 single-parameter, no-output-schema operation, the description covers the action, its scope ('every marker'), and the confirmation behavior. Nothing critical is missing, though it does not say what happens if a marker is already off or how failures are surfaced during the readback.

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% for the single 'instrument' parameter, including its default resolution, so the schema carries the parameter burden. The description mentions nothing about parameter selection, but the baseline of 3 applies when the schema is this complete.

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?

The description names a specific verb and resource ('Turn every EMI marker off') and even supplies the underlying SCPI command (:CALCulate:FSCan:MARKer:AOFF), so intent is unambiguous. It does not explicitly distinguish itself from near-identical siblings such as markers_all_off or ad_markers_all_off, leaving the domain distinction to be inferred from the word 'EMI'.

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 rather than stated: an agent can infer this is the bulk-off operation for EMI markers, as opposed to set_emi_marker for individual control. There is no explicit when-to-use/when-not-to-use guidance or mention of prerequisites, but nothing is misleading.

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