Skip to main content
Glama
lucasgerads

LeCroy Oscilloscope MCP

by lucasgerads

scope_disconnect

Disconnect from the LeCroy oscilloscope safely, with no errors if already disconnected.

Instructions

Disconnect from the oscilloscope. Safe to call even if not connected.

Transport: local

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The scope_disconnect MCP tool handler. Calls _scope.disconnect() on the module-level LeCroyScope singleton and returns 'Disconnected.'
    @mcp.tool()
    def scope_disconnect() -> str:
        """Disconnect from the oscilloscope. Safe to call even if not connected.
    
        Transport: local
        """
        _scope.disconnect()
        return "Disconnected."
  • server.py:363-371 (registration)
    Registered as an MCP tool via @mcp.tool() decorator on the scope_disconnect function. Defined in server.py using FastMCP.
    @mcp.tool()
    def scope_disconnect() -> str:
        """Disconnect from the oscilloscope. Safe to call even if not connected.
    
        Transport: local
        """
        _scope.disconnect()
        return "Disconnected."
  • The underlying LeCroyScope.disconnect() method called by the MCP tool handler. Closes VISA connection gracefully, resets internal state to defaults.
    def disconnect(self) -> None:
        """Close VISA connection gracefully."""
        for obj in (self._inst, self._rm):
            if obj:
                try:
                    obj.close()
                except Exception:
                    pass
        self._inst = None
        self._rm = None
        self._idn = None
        self._model = None
        self.profile = DEFAULT_PROFILE
Behavior4/5

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

With no annotations, the description provides meaningful behavioral info: it is safe to call when not connected, indicating idempotency. This adds value beyond the bare 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?

Two concise sentences front-load the purpose, with zero wasted 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 parameterless disconnect tool with an output schema, the description is sufficient. It explains safety, though it could mention return value behavior.

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

Parameters4/5

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

Input schema has no parameters with 100% coverage, so baseline is 4. The description does not need to add parameter info, and it does not.

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 'Disconnect from the oscilloscope' using a specific verb and resource, and distinguishes itself from siblings like 'scope_connect' and 'scope_connection_status'.

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?

The description notes it is 'Safe to call even if not connected', providing clear usage context and implying idempotency, though it does not explicitly mention when not to use it.

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