Skip to main content
Glama
nk-dho924s-mcp

nk-dho924s-mcp

by bigtimer-dev

set_channel

Change selected settings for an oscilloscope channel, including coupling, display, scale, offset, probe, and invert, and return the updated channel state.

Instructions

Change channel settings; only the given ones are changed. Returns the new channel state.

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": {
      "channel": "<channel>"
    },
    "name": "set_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
probeNo
invertNo
channelYes
displayNo
couplingNo
offset_vNo
scale_v_divNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden, and it does disclose two genuinely useful traits: it is a partial mutation that leaves unspecified settings untouched, and it returns the resulting channel state. It omits permission requirements, whether changes take effect on a live acquisition, and how out-of-range or invalid values are handled — meaningful gaps for a hardware-mutating tool.

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?

Two short sentences with zero filler, and the mutation-plus-scope statement is front-loaded ahead of the return-value note. Nothing is redundant.

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?

Placeholder note: an output schema exists, so the return-value needn't be described in more detail. However, for a seven-parameter tool with no annotations and zero schema coverage, the description leaves too much unexplained to be called complete; it should at minimum sketch what the numeric and enum settings mean.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across seven parameters (probe, invert, display, coupling, offset_v, scale_v_div, channel), so the description needs to compensate and does not. It never explains units, valid ranges, or what the DC/AC/GND enum means. The only inferred meaning is that every setting besides channel is optional, from 'only the given ones are changed.'

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 uses a specific verb ('Change') with a specific resource ('channel settings'), which distinguishes it from siblings like set_timebase or set_trigger. It stops short of explicitly naming those alternatives, so it lands at a clear-but-undifferentiated 4.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to reach for this tool versus the other setters, and no prerequisites or exclusions are mentioned. The only usage-relevant hint is the partial-update note ('only the given ones are changed'), which tells you not to resend all settings but does not route the agent among alternatives.

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