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

uni-t-uts-mcp

by Reid-n0rc

emi_signal_list

Edits the EMI peak/signal table: add marker frequencies or measurements, replace/append meter readings, delete/mark signals, set marker meter coupling, and zoom the list.

Instructions

Act on the EMI module's signal table (peak table): add the current marker's frequency or measurement to the list, replace or append a row from a meter reading, delete or mark/unmark a signal, set which meter a marker couples to, or zoom the list view. The manual documents NO command to read the table's contents and none of these actions has a read-back, so the result only confirms the command was accepted (no instrument error); to see the actual list, use the screenshot tool over VXI-11.

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": {
      "action": "<action>"
    },
    "name": "emi_signal_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
meterNoMeter number (replace_with_meter, set_meter)
actionYesWhich signal-list action to run
markerNoMarker number (add_marker)
signalNoSignal number (delete, mark, clear_mark; optional for zoom_in/zoom_out)
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.7/5.0
Behavior5/5

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

With only readOnlyHint=false supplied, the description carries the real disclosure burden and does it well: it states that no action has a read-back, that the return value only confirms command acceptance (no instrument error), and that deletions/marks are not observable. That is behavior an agent cannot infer from the annotation or the schema and directly affects how it should sequence work.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action list and then the critical return-value constraint. The long first sentence is a dense enumeration of distinct operations rather than filler, and every clause in the second sentence changes how the agent must behave.

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?

There is no output schema, and the description compensates by explaining exactly what a call returns (acceptance confirmation, not list contents) and how to obtain the actual data. For a five-parameter mutation tool with a single annotation, nothing an agent needs in order to call it correctly and interpret the result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning beyond it by explaining the distinction between add_marker (adds the marker's frequency) and add_marker_measurement (adds the measurement), and by clarifying the meter-coupling and zoom semantics. It does not document ranges or the marker/signal numbering constraints, which the schema already covers.

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?

Names the specific resource (EMI module's signal table / peak table) and enumerates concrete verb-level operations: add marker frequency, replace/append from a meter reading, delete, mark/unmark, couple a meter, zoom. The parenthetical "(peak table)" disambiguates the resource from near-neighbors like the sort tools, so an agent can identify it without opening the schema.

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?

Explicitly routes the agent away from using this tool to read data and toward the screenshot tool over VXI-11, which is exactly the alternative-selection guidance that matters here. It stops short of distinguishing when to choose specific actions over sibling tools like get_emi_signal_list_sort or set_emi_signal_list_sort, which are the closest functional neighbors.

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