scpi-mcp

Overview Schema Source Related Servers Discussions Admin

set_trigger

Configure edge trigger by setting source channel, voltage level, and slope direction to stabilize repetitive signals or capture single-shot events on the desired edge.

Instructions

Configure the edge trigger (source channel, level, slope).

Sets up a stable trigger so repetitive signals hold still, or so a
single-shot (see acq_single) fires on the right edge of a one-off event.

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": {
      "source": "<source>",
      "level": "<level>"
    },
    "name": "set_trigger"
  }
}

Input Schema

Name	Required	Description	Default
`level`	Yes	Trigger threshold voltage. The scope fires when the source crosses this level in the chosen slope direction.
`slope`	No	Edge direction to trigger on: 'rising' (default) or 'falling'.	rising
`source`	Yes	Trigger source: analog channel to trigger on (1-based).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.1.1Jul 7, 2026

removedInput schema / properties / args
```
Removed value: -{
-  "title": "Args"
-}
```

removedInput schema / properties / kwargs

Removed value: -{
-  "title": "Kwargs"
-}

addedInput schema / properties / level

Added value: +{
+  "description": "Trigger threshold voltage. The scope fires when the source crosses this level in the chosen slope direction.",
+  "title": "Level",
+  "type": "number"
+}

addedInput schema / properties / slope

Added value: +{
+  "default": "rising",
+  "description": "Edge direction to trigger on: 'rising' (default) or 'falling'.",
+  "title": "Slope",
+  "type": "string"
+}

addedInput schema / properties / source

Added value: +{
+  "description": "Trigger source: analog channel to trigger on (1-based).",
+  "title": "Source",
+  "type": "integer"
+}

changedInput schema / required

Previous value: -[
-  "args",
-  "kwargs"
-]New value: +[
+  "source",
+  "level"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "set_trigger_implDictOutput",
+  "type": "object"
+}

First observedv0.1.0Jun 21, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations provided, so description must carry the burden. It describes the action (configuring trigger) and the effect (sets up stable trigger). However, it does not disclose potential side effects (e.g., overriding previous trigger settings) or read-only nature.

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?

Three sentences, no redundancy, front-loaded with purpose. Every sentence adds value.

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?

Given 3 parameters and output schema existence, the description sufficiently explains the tool's usage. Could mention the output briefly, but not required due to output schema.

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%, baseline 3. Description adds context for 'level' (threshold voltage) and 'source' (1-based) but largely paraphrases the schema. No additional meaning beyond schema.

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

Purpose5/5

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

Description clearly states verb+resource ('configure the edge trigger') and explains the purpose with concrete use cases (stabilize repetitive signals, single-shot). Distinguishes from sibling 'acq_single' by mentioning it.

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

Usage Guidelines4/5

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

Provides clear context for using the tool (stabilizing repetitive signals or for single-shot events) and references sibling 'acq_single'. Could be more explicit about when not to use, but sufficient.

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

Deploy Server