Skip to main content
Glama
lucasgerads

LeCroy Oscilloscope MCP

by lucasgerads

scope_set_tdiv

Set the time per division on a LeCroy oscilloscope to control the horizontal scale, enabling precise waveform viewing and measurement.

Instructions

Set the time base (time per division).

Args: seconds_per_div: Time/div in seconds. Examples: 1e-9 (1 ns), 1e-6 (1 µs), 1e-3 (1 ms), 1.0 (1 s)

Transport: SCPI

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seconds_per_divYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler function 'scope_set_tdiv' — sets the time base (time per division) on the oscilloscope. Calls _scope.set_tdiv(seconds_per_div) under the VISA lock.
    @mcp.tool()
    def scope_set_tdiv(seconds_per_div: float) -> str:
        """Set the time base (time per division).
    
        Args:
            seconds_per_div: Time/div in seconds.
                Examples: 1e-9 (1 ns), 1e-6 (1 µs), 1e-3 (1 ms), 1.0 (1 s)
    
        Transport: SCPI
        """
        return _run(lambda: _scope.set_tdiv(seconds_per_div))
  • Low-level SCPI helper 'set_tdiv' — sends 'TDIV <seconds_per_div>' command to the oscilloscope.
    def set_tdiv(self, seconds_per_div: float) -> None:
        self.write(f"TDIV {seconds_per_div:.6E}")
  • Input schema — takes a single float parameter 'seconds_per_div' representing time/div in seconds. Docstring describes valid examples (1e-9 for 1 ns, 1e-3 for 1 ms, etc.).
    def scope_set_tdiv(seconds_per_div: float) -> str:
        """Set the time base (time per division).
    
        Args:
            seconds_per_div: Time/div in seconds.
                Examples: 1e-9 (1 ns), 1e-6 (1 µs), 1e-3 (1 ms), 1.0 (1 s)
    
        Transport: SCPI
        """
Behavior2/5

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

No annotations provided, so the description must cover behavioral traits. It only adds 'Transport: SCPI' but omits side effects, reversibility, or required device state.

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?

Short and front-loaded with the main purpose. Could benefit from a more structured format (e.g., separating parameter description) but no unnecessary words.

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?

For a simple setter with one parameter, the description covers the parameter well and includes transport info. Output schema exists so return values are not required. Missing behavioral context slightly lowers the score.

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?

Schema coverage is 0%, so description must compensate. It explains the parameter 'seconds_per_div' clearly, provides units (seconds), and gives concrete examples (1e-9, 1e-6, etc.).

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 verb 'Set' and the resource 'time base (time per division)'. This distinguishes it from siblings like scope_timebase_info which queries instead of sets.

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 vs alternatives (e.g., scope_timebase_info to check current setting). No prerequisites or conditions for use are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lucasgerads/lecroy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server