Skip to main content
Glama
zinntikumugai

rigol-oscilloscope-mcp

by zinntikumugai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

configure_decode

Set up serial protocol decoding on a selected bus, choosing protocol, data format, and optional settings while keeping unspecified parameters unchanged.

Instructions

Configure a serial protocol decode bus. Omitted items are left unchanged.

The bus count is model-dependent (get_capabilities decode_buses; 4 on MHO98).

protocol is uart / i2c / spi / can / lin / parallel (options such as I2S, FlexRay, MIL-STD-1553 and CAN-FD are not supported). data_format is hex / ascii / dec / bin. Source values are "CH1"-"CH4", "D0"-"D15" or "off".

settings keys per protocol (all optional):

  • uart: tx_source, rx_source, baud_bps, data_bits, parity (none/odd/even), stop_bits (1/1.5/2), endian (msb/lsb), polarity (positive/negative), tx_threshold_v, rx_threshold_v. Example: {"tx_source": "CH1", "baud_bps": 115200, "data_bits": 8, "parity": "none", "stop_bits": 1, "tx_threshold_v": 1.65}

  • i2c: scl_source, sda_source, swap_sda_scl, address_bits (7/8/10), scl_threshold_v, sda_threshold_v. Example: {"scl_source": "CH1", "sda_source": "CH2", "address_bits": 7}

  • spi: clk_source, clk_slope (rising/falling), mosi_source, miso_source, cs_source, cs_polarity (high/low), frame_mode (cs/timeout), timeout_s, data_bits (4-32), endian, polarity (high/low), clk_threshold_v, mosi_threshold_v, miso_threshold_v, cs_threshold_v. Example: {"clk_source": "CH1", "mosi_source": "CH2", "data_bits": 8}

  • can: source, signal_type (tx/rx/canh/canl/differential), baud_bps, sample_point_percent, threshold_v. Example: {"source": "CH1", "signal_type": "canh", "baud_bps": 500000}

  • lin: source, baud_bps, parity_enabled, standard (v1x/v2x/mixed), threshold_v. Example: {"source": "CH1", "baud_bps": 19200, "standard": "v2x"}

  • parallel: clk_source, clk_slope, bus (d7_d0/d15_d8/d15_d0/d0_d7/ d8_d15/d0_d15/ch1-ch4/user), bus_width (1-16), bit_sources, endian, polarity. bus is the data source; the digital groups list the MSB first. bus_width and bit_sources only work while bus is "user" (the device rejects them otherwise), so set bus in the same call. bit_sources is a list of "CH1"-"CH4" / "D0"-"D15", one per data bit starting at bit 0, and no longer than bus_width. Example: {"bus": "user", "bus_width": 2, "bit_sources": ["CH1", "CH2"]}

Set event_table=true (together with enabled=true) before reading the decoded results with get_decode_result. This only changes what the device displays and analyses: acquisition settings are untouched, so configure the channels and trigger separately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
busNo
enabledNo
protocolYes
settingsNo
data_formatNo
event_tableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so thoroughly. It discloses that omitted items remain unchanged, that unsupported protocol variants are rejected, that parallel bus_width/bit_sources only work when bus='user' and will be rejected otherwise, and that the tool only changes display/analysis behavior, not acquisition settings.

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?

The description is long but appropriately so given the complex settings object. It is front-loaded with the core purpose, then organized into general parameter rules and per-protocol subsections with examples. Every section adds essential information; there is no filler or repetition.

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

Completeness5/5

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

Despite having no output schema and minimal input schema, the description is complete for calling the tool correctly. It specifies model-dependent bus counts, supported protocols, all relevant settings per protocol, required sequencing for event_table, and the boundary between decode configuration and acquisition configuration.

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

Parameters5/5

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

The input schema has 0% description coverage and no enums, so the description is the sole source of parameter meaning. It fully compensates by defining protocol values, data_format values, source values, and providing detailed per-protocol settings keys with concrete examples for each protocol.

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?

The first sentence states a specific action and resource: 'Configure a serial protocol decode bus.' This clearly distinguishes it from sibling configure_* tools like configure_channel and configure_trigger, and the rest of the description reinforces that scope by listing protocol types and settings.

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

Usage Guidelines5/5

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

The description gives explicit usage context: it notes the bus count can be checked via get_capabilities, instructs setting event_table=true before using get_decode_result, and clearly states that acquisition settings are untouched so channels and trigger must be configured separately. This provides both when-to-use and when-not-to-use guidance.

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