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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_ad_marker

Read-only

Reads one AD marker's mode, trace, x/y position, and value with units; requires an active AD module and handles markers 1–6, delta reference offsets, and off states.

Instructions

Read one AD marker: mode (off, normal, delta, fixed), trace, and its position (x) and value (y) together, with their units (which depend on the trace and current demod type). AD module must be active. A delta marker's x/y are relative to its reference marker. An off marker has x and y null. Live-verified (2026-11-12).

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

Input Schema

NameRequiredDescriptionDefault
markerNoMarker number, 1 to 6 (AD has six markers per demod type, not SA's ten)
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=true, so safety is covered; the description goes further by disclosing that a delta marker's x/y are relative to a reference marker, that an off marker returns null x/y, and that units depend on trace and demod type. These are non-obvious return-value behaviors an agent could not get from the schema, and it flags the definition as live-verified. It stops short of describing error behavior when the AD module is inactive.

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 core read is front-loaded in the first clause, and the field list and semantic caveats follow in tight order. It is somewhat run-on with stacked parentheticals, and the 'Live-verified (2026-11-12)' tag adds little for tool selection, but no sentence is wasted.

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?

With no output schema, the description carries the burden of explaining return values and does so well, covering mode, trace, paired x/y, units, and the null cases. The precondition on the AD module is stated, so an agent has enough to invoke it correctly; only failure-mode details are absent.

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 coverage is 100%, so both the marker number and instrument selection are already documented in the schema, including the 1-6 range and the SA contrast. The description adds nothing about parameter syntax or defaults, which is acceptable given the schema's completeness but is baseline-level value.

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 AD marker') and enumerates the returned fields (mode, trace, x, y, units), so the agent knows exactly what comes back. The 'AD' qualifier distinguishes it from the SA marker family by context, though no sibling is named explicitly as the wrong tool to use.

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?

It gives one concrete precondition ('AD module must be active'), which is useful gating context. However, it never states when to prefer this over get_marker, get_emi_marker, or marker_search, leaving the agent to infer the choice from the 'AD' prefix alone.

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