Skip to main content
Glama
nk-dho924s-mcp

nk-dho924s-mcp

by bigtimer-dev

set_trigger

Configure oscilloscope edge trigger settings such as source, slope, sweep, and voltage level; only supplied parameters are changed, and the resulting trigger state is returned.

Instructions

Edge trigger settings; only given ones are changed. Returns the trigger state.

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

Input Schema

NameRequiredDescriptionDefault
slopeNo
sweepNo
sourceNo
level_vNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful behaviors: only the supplied settings are modified (partial update, no reset of omitted fields) and the trigger state is returned. It omits important behavior for a mutation on an instrument — whether the scope must be idle, whether other trigger types are supported, and any side effects on acquisition — so meaningful gaps remain.

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, front-loaded with the purpose and then the update semantics, with no filler. It is efficient, though efficiency here comes at the cost of under-specification rather than from pruning redundant content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the return value needs no further explanation, but for a four-parameter mutation tool with zero annotation coverage and zero schema description coverage the description is far too thin. An agent learns nothing about what each setting controls or what operational state the call requires.

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%, so the description must explain slope, sweep, source, and level_v, and it explains none of them; the enum values in the schema appear but are themselves undocumented. The single added semantic is that parameters are optional partial overrides ("only given ones are changed"), which is slight compensation for four undocumented parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Edge trigger settings" names the resource (edge trigger configuration) but is a noun fragment with no verb; the action is only inferable from the name set_trigger. It does distinguish it from siblings like set_channel or set_timebase by naming the trigger subsystem, so an agent can roughly tell what it configures, but the statement of purpose is vague rather than a complete verb+resource claim.

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?

The description gives no when-to-use context, no prerequisites (e.g., whether acquisition must be stopped), and no alternatives among the sibling tools. The only guidance-like content is a partial-update rule, which describes mechanics rather than when to call the tool.

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