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

uni-t-uts-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_frequency_counter

Idempotent

Turn a marker frequency counter on or off and set its gate time from 1 µs to 500 ms, reporting any values the instrument changed.

Instructions

Turn the marker frequency counter on or off and/or set its gate time (1 us to 500 ms). Values the instrument changed are reported in 'warnings'.

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

Input Schema

NameRequiredDescriptionDefault
enabledNoCounter on or off
instrumentNoWhich instrument to use (a name from list_instruments). Default: the `default` instrument, or the only one configured
gate_time_sNoGate time in seconds, 1e-6 to 0.5

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, so safety and repeatability are covered. The description adds genuine value beyond that by noting that instrument-corrected values are surfaced in 'warnings', which is otherwise undisclosed since there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence plus a short clause, with the primary action front-loaded and no filler. The 'and/or' construction efficiently conveys that either parameter can be set independently.

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-optional-parameter setter with no output schema, the definition covers the action, the bounded range, and where corrective feedback appears. It stops short of saying what conditions are required for a counter to exist or what the warnings mean operationally.

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 enabled, instrument, and gate_time_s are already documented. The description only restates the gate range in human units (1 us to 500 ms) against the schema's seconds value, a small mapping aid rather than new semantic content.

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 gives a specific verb and resource: turn the marker frequency counter on or off and set its gate time. It is clearly distinct from the read-side sibling get_frequency_counter (set vs. get), though it never names that sibling explicitly.

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 the verb – an agent can infer this is the write path for the frequency counter. There is no statement of prerequisites (e.g. an active marker), nor an explicit 'use this instead of X' routing, and no exclusions.

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