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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_emi_scan_table

Idempotent

Configure or edit the EMI module's 10-band scan table, including per-band frequency, RBW, sweep time, attenuation, points, preamp, and enabled state, or load CISPR A-E presets.

Instructions

Edit the EMI module's 10-band scan table: per band, enabled, start_hz, stop_hz, rbw_hz/rbw_auto, time_s/time_auto, attenuation_db/attenuation_auto, points (11-40001) and preamp; or load a CISPR band preset (presets: band, cis: A/B/C/D/CD/E). EMI module must be active (select_instrument_module). The whole table is re-read afterwards and anything adjusted by the instrument (including the neighbor-band coupling the manual describes on overlap or crossing) is reported in 'warnings'.

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

Input Schema

NameRequiredDescriptionDefault
bandsNoPer-band edits; give only the fields to change for each band
presetsNoLoad a CISPR band preset into a band (applied before any bands edits for the same band number)
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.2/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the post-write re-read, that instrument-side adjustments (neighbor-band coupling on overlap/crossing) surface in 'warnings', and the module-active precondition. This is real behavioral context for a mutation tool. Minor gap: it never states what happens to bands omitted from the payload or how errors surface.

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?

Dense but front-loaded: the object of the edit comes first, then the preset alternative, then prerequisites, then post-condition. Some duplication of schema-stated ranges (points 11-40001, presets A/B/C/D/CD/E) is wasted space, and the single-sentence form makes the prerequisite easy to skim past.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 takes on the job of explaining the return surface ('warnings' after a re-read), and it covers the activation precondition for a mutation on a shared instrument state. Nothing an agent needs in order to call this safely appears to be missing.

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 three top-level parameters and every nested band field are already documented, including ranges and the auto-flag interactions. The description largely restates those field names and the points range rather than adding new meaning, so baseline 3 applies.

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?

States a specific verb+resource ('Edit the EMI module's 10-band scan table') and enumerates exactly what can be changed per band, plus the alternative preset-loading mode. An agent can distinguish this from siblings like set_emi_measurement or get_emi_settings purely from the text.

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?

Names the prerequisite explicitly ('EMI module must be active (select_instrument_module)'), giving both a condition and the sibling that satisfies it, and clarifies the two usage modes (per-band edits vs. CISPR presets). It does not, however, say when not to use it or contrast it with the get_emi_* readers.

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