Skip to main content
Glama
Sign In
rigol-dho-mcp

rigol-dho-mcp

by mattjax16
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

configure_timebase

Set the horizontal timebase scale and offset to control the waveform display on a Rigol oscilloscope.

Instructions

Set the main horizontal timebase scale and/or offset.

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": "configure_timebase"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNoMain timebase in s/div, e.g. 0.0002 for 200 µs/div
offsetNoHorizontal offset in seconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

The description does not disclose behavioral traits such as side effects, required permissions, or whether the change takes effect immediately. With no annotations provided, the description fails to inform about behavior beyond the basic action.

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?

A single sentence that conveys the core function without unnecessary words. It is appropriately short and front-loaded.

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?

The description lacks information about constraints, valid ranges, or the effect on other settings. Given the tool's role in configuring an oscilloscope, the description should provide more context for correct usage.

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?

The schema provides descriptions for both parameters (scale and offset). The description repeats the parameter names but adds no additional semantic meaning. Baseline 3 given 100% schema coverage.

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 description clearly states the action (set) and the resource (main horizontal timebase scale and/or offset). It is specific and distinct from sibling tools like configure_channel or configure_acquisition.

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?

No guidance on when to use this tool versus alternatives. The description only states the action without context about usage scenarios or prerequisites.

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