MHO98 MCP Server

Overview Schema Source Related Servers Discussions Admin

configure_bus_m1553

Configures an oscilloscope bus for MIL-STD-1553B decoding by selecting the source channel or digital line and enabling display. Use it to set up 1553 bus analysis on a Rigol MHO98.

Instructions

Set Bus to MIL-STD-1553B decoding and configure it (manual 3.4.18).

source: 1553 bus line source CH1..CH4 or D0..D15 display: enable the decoding bus (Set the differential threshold via configure_bus(threshold=..., threshold_type='1553').)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bus`	Yes
`source`	No
`display`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full transparency burden. It discloses that this enables decoding and defines source/display behavior, but does not mention side effects, overwrites, required state, or other operational constraints.

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?

Front-loaded purpose followed by parameter notes and a useful routing note for threshold configuration. It is concise and skimmable, though the fragment style and manual citation are slightly rough.

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

Completeness3/5

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

Output schema exists, so return values need not be described. However, with no annotations and 0% schema description coverage, the description leaves gaps: the bus parameter range/meaning, defaults, and preconditions are not addressed.

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 description coverage is 0%, so the description must compensate. It explains source options (CH1..CH4 or D0..D15) and display meaning, but does not define the required bus parameter beyond the vague '<n>' placeholder.

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?

States a specific verb and resource: setting a bus to MIL-STD-1553B decoding and configuring it. The tool is clearly one of the bus-protocol configuration siblings, and the manual reference reinforces scope.

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 implied by the tool name and the phrase 'Set Bus <n> to MIL-STD-1553B decoding.' It explicitly redirects differential-threshold configuration to configure_bus, but does not state when to prefer this tool over other bus configuration tools or what prerequisites exist.

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

Deploy Server