Skip to main content
Glama
markuskreitzer

PicoScope MCP Server

get_device_info

Retrieve detailed specifications and capabilities of the connected PicoScope oscilloscope, including model, serial number, variant, and supported features.

Instructions

Get detailed information about the currently connected device.

Returns: Dictionary containing device model, serial, variant, capabilities, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_device_info' tool. It checks if a device is connected, retrieves device information using device_manager.get_info(), and returns a structured dictionary with status and device details.
    @mcp.tool()
    def get_device_info() -> dict[str, Any]:
        """Get detailed information about the currently connected device.
    
        Returns:
            Dictionary containing device model, serial, variant, capabilities, etc.
        """
        try:
            if not device_manager.is_connected():
                return {
                    "status": "error",
                    "error": "No device connected",
                    "connected": False,
                }
    
            info = device_manager.get_info()
            if info:
                return {
                    "status": "success",
                    "connected": True,
                    "device": {
                        "model": info.model,
                        "serial": info.serial,
                        "variant": info.variant,
                        "batch_and_serial": info.batch_and_serial,
                        "num_channels": info.num_channels,
                        "max_adc_value": info.max_adc_value,
                        "min_adc_value": info.min_adc_value,
                    },
                }
            else:
                return {
                    "status": "error",
                    "error": "Failed to retrieve device info",
                }
    
        except Exception as e:
            return {
                "status": "error",
                "error": str(e),
            }
  • Invocation of register_discovery_tools which defines and registers the get_device_info tool using the @mcp.tool() decorator.
    register_discovery_tools(mcp)
Behavior3/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a read operation ('Get') and describes the return format, which is helpful. However, it doesn't mention potential errors (e.g., if no device is connected), performance characteristics, or whether this requires specific permissions—leaving gaps for a mutation-free tool.

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 perfectly concise and well-structured: a single clear purpose statement followed by a brief returns section. Every sentence earns its place by providing essential information without redundancy or fluff, making it easy to scan and understand.

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?

Given the tool's simplicity (no parameters, read-only operation) and the presence of an output schema (which handles return value documentation), the description is reasonably complete. It covers the core purpose and return format. However, it could be slightly more complete by mentioning error conditions or connection prerequisites.

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?

The tool has zero parameters with 100% schema description coverage, so the schema already fully documents the input requirements. The description appropriately doesn't waste space discussing parameters, maintaining focus on what the tool does rather than how to call it. A baseline of 4 is appropriate for zero-parameter tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('detailed information about the currently connected device'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_devices' or 'get_channel_config', which would be needed for a perfect score.

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?

The description implies usage context by specifying 'currently connected device', suggesting this tool should be used after establishing a connection. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'list_devices' (which might show available devices) or mention prerequisites like needing to call 'connect_device' first.

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/markuskreitzer/picoscope_mcp'

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