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

uni-t-uts-mcp

by Reid-n0rc

marker_to_instrument

Set an instrument parameter—center, step, start, stop, or reference level—from an active marker's frequency or level. Choose the marker and target parameter; the tool returns the updated value.

Instructions

Use a marker's frequency or level to set an instrument parameter: center, step (center frequency step; turns automatic step off), start, stop or reference_level. The marker must be on. Returns the new value of the parameter. The instrument refuses a center that would put the span outside its range.

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": {
      "marker": "<marker>",
      "target": "<target>"
    },
    "name": "marker_to_instrument"
  }
}

Input Schema

NameRequiredDescriptionDefault
markerYesMarker number, 1 to 10
targetYesParameter to set from the marker
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 only tell the agent this is not read-only; the description goes further by disclosing the return value (the new parameter value), a side effect (targeting 'step' turns automatic step off), and an instrument-side rejection condition. It does not explain what happens to the marker itself or what error form the refusal takes, but the added behavioral context is substantial for a mutation tool.

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?

Purpose is front-loaded in the first clause, followed by the target list, precondition, return value, and failure case in a compact four-sentence block. The only mild weakness is that the parenthetical for 'step' is compressed enough to require a re-read.

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 three-parameter mutation tool with minimal annotations and no output schema, the definition covers precondition, side effect, return value, and one error path, which is close to sufficient. Still missing is any statement about measurement state requirements or what the agent should do when the marker is off or the center is rejected.

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 the schema already carries the baseline documentation and the enum values. The description contributes real meaning only for 'step' (center frequency step, disables automatic step) and the span-range constraint on 'center'; 'start', 'stop', and 'reference_level' are listed without further semantics, and the default/instrument parameter is left entirely to the schema.

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 names a specific source (a marker's frequency or level) and an explicit destination set (center, step, start, stop, reference_level), so the verb+resource is unambiguous. It stops short of naming the sibling it supersedes (e.g., set_marker, get_marker), so an agent must infer the boundary from the parameter list alone.

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 supplies a real precondition ("The marker must be on") and one failure case (center that would push the span out of range), which is genuine usage guidance. However, it never says when to prefer this tool over directly setting an instrument parameter or over the marker-manipulation siblings, leaving the selection decision implicit.

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