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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_emi_limit_line

Read-only

Retrieve an EMI limit line's display state, upper/lower type, tested trace, margin, and frequency/level points so you can inspect compliance settings and compare them with trace data.

Instructions

Read one EMI limit line: whether it is displayed, its type (upper or lower), the trace it is tested against, the margin and its on/off state, and the point list (frequency in Hz, level in dBm, connected). EMI module must be active (select_instrument_module). The analyzer documents no pass/fail read-back, so whether a trace violates the line cannot be read; check the screenshot or compare get_trace_data with the points.

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

Input Schema

NameRequiredDescriptionDefault
lineNoLimit line number, 1 to 6 (EMI mode has only 3 traces to test against, see 'trace')
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.4/5.0
Behavior5/5

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

The readOnlyHint annotation is consistent with a read tool, and the description goes well past it: it discloses that the analyzer exposes no pass/fail read-back, so violation status cannot be obtained, and it names two workarounds. It also lists the full field set returned, including units (Hz, dBm) and the 'connected' flag.

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?

The purpose sentence is front-loaded, the prerequisite follows, and the limitation with its workarounds comes last – a sensible order. The middle enumeration of returned fields is a long comma chain but each item is informative, so it earns its place.

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, so the description must carry the return shape itself, and it does so field by field. Combined with the module-active precondition and the pass/fail caveat, an agent has everything needed to call this correctly and interpret the result.

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% and both parameters carry their own descriptions, including the 1-6 range and the note that EMI mode has only three traces, so the baseline is 3 by rule. The description adds little about the `line` argument beyond what the schema states and says nothing at all about `instrument`.

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 opens with a specific verb and resource ("Read one EMI limit line") and then enumerates the exact contents of that read: display state, upper/lower type, tested trace, margin and on/off state, and the point list with units. This clearly separates it from the set_emi_limit_line, delete_emi_limit_line, and get_limit_line siblings without requiring the reader to open any 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?

It states a concrete precondition that must hold before the call (the EMI module must be active, via select_instrument_module) and gives explicit alternatives when the user's real question is pass/fail: consult the screenshot or compare get_trace_data with the points. It does not explain when to prefer this over the non-EMI get_limit_line sibling, which keeps it short of a 5.

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