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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_marker_function

Read-only

Reads a spectrum analyzer marker's function (off, noise, band power, band density) and the band span used by band functions; use get_marker (y) to read the resulting level.

Instructions

Read a marker's function (off, noise, band_power, band_density) and the band span used by the band functions. The function result is the marker's level: read it with get_marker (y).

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

Input Schema

NameRequiredDescriptionDefault
markerNoMarker number, 1 to 10
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?

The readOnlyHint annotation already establishes this as a safe read, so the description's main added value is disclosing the return payload: the function value plus the band span used by the band functions. It does not describe behavior for edge cases (e.g., what band span means when the function is 'off' or 'noise'), nor error behavior for an invalid marker. Useful context, but thin beyond the annotation.

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?

Two short sentences with the core capability front-loaded and no filler. The second sentence is a little awkwardly phrased but earns its place by disambiguating against get_marker.

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 simple read-only getter with full schema coverage and no output schema, the description covers the essential return values (function enum and band span) that the agent otherwise could not know. Minor gaps remain around behavior when the function is off or when the marker is invalid, but nothing critical for correct invocation is 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 both parameters (marker number 1-10, instrument selection) are fully documented in the schema. The description adds no further meaning about either parameter, which is acceptable given the schema already carries that burden.

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?

States a specific verb ('Read') and resource ('a marker's function') and enumerates the possible function values (off, noise, band_power, band_density), which is far more than the title alone conveys. It also explicitly separates itself from get_marker by noting the level is fetched there instead. The second sentence ('The function result is the marker's level: read it with get_marker (y)') is slightly convoluted, keeping it just below top marks.

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?

The description implies usage by routing the agent to get_marker for the level value, which is a partial alternative-selection hint. It never states when to call this versus set_marker_function, nor any prerequisites or exclusions. Usage is inferable but not spelled out.

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