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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_emi_marker

Read-only

Read one of six EMI markers to retrieve its mode, trace, frequency, and level together, including delta-relative coordinates and null values when off.

Instructions

Read one EMI marker: mode (off, normal, delta, fixed), trace (1-3) and its frequency (x, Hz) and level (y, dBm by default) together. A delta marker's x and y are relative to its reference marker. An off marker has x and y null.

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_marker"
  }
}

Input Schema

NameRequiredDescriptionDefault
markerNoMarker number, 1 to 6 (EMI has 6 markers)
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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine behavioral context beyond that: delta markers report relative x/y and an off marker returns null x/y, which prevents misinterpretation of the returned values. It stops short of stating what happens for an invalid marker number or an unconfigured instrument.

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?

Three short sentences, front-loaded with the core action and then the value semantics. Every clause carries information; only the parenthetical unit notes slightly crowd the opening sentence.

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 two-parameter read tool with full schema coverage and no output schema, the description adequately defines the returned tuple, including the mode-dependent meaning of x and y. The main residual gap is the absence of any guidance on error or empty conditions.

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%, with the marker range (1-6) and the instrument/default-instrument behavior already documented in the schema. The description adds nothing about either parameter, so the baseline of 3 applies.

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 opens with a specific verb and resource ('Read one EMI marker') and enumerates exactly what comes back: mode, trace, frequency and level. It is clearly a single-marker read rather than a bulk/multi-marker operation, though it never names a sibling it is distinct from.

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 only implied by 'Read one EMI marker' — an agent can infer this is the per-marker getter rather than set_emi_marker or emi_marker_search, but no explicit when-to-use, when-not-to-use, or alternative routing is stated.

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