Skip to main content
Glama
markuskreitzer

PicoScope MCP Server

by markuskreitzer
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

measure_pulse_width

Measure pulse width at a specified threshold on PicoScope oscilloscope channels to analyze signal timing characteristics.

Instructions

Measure pulse width at specified threshold.

Args: channel: Channel to measure. threshold_percent: Threshold percentage for pulse measurement (0-100).

Returns: Dictionary containing pulse width in seconds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYes
threshold_percentNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/picoscope_mcp/tools/analysis.py:122-140 (handler)
    The handler function for the 'measure_pulse_width' tool, decorated with @mcp.tool() for registration. Includes input schema via type hints and a stub implementation.
    @mcp.tool()
def measure_pulse_width(
    channel: Literal["A", "B", "C", "D"], threshold_percent: float = 50.0
) -> dict[str, Any]:
    """Measure pulse width at specified threshold.

    Args:
        channel: Channel to measure.
        threshold_percent: Threshold percentage for pulse measurement (0-100).

    Returns:
        Dictionary containing pulse width in seconds.
    """
    # TODO: Implement pulse width measurement
    return {
        "status": "not_implemented",
        "channel": channel,
        "threshold": threshold_percent,
    }
  • src/picoscope_mcp/server.py:8-18 (registration)
    Imports and calls register_analysis_tools(mcp), which registers the analysis tools including 'measure_pulse_width'.
    from .tools.analysis import register_analysis_tools
from .tools.advanced import register_advanced_tools

# Create FastMCP server instance
mcp = FastMCP("PicoScope MCP Server")

# Register all tool categories
register_discovery_tools(mcp)
register_configuration_tools(mcp)
register_acquisition_tools(mcp)
register_analysis_tools(mcp)

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool measures pulse width but does not disclose behavioral traits such as required device state (e.g., connected device, active signal), measurement accuracy, error conditions, or side effects. The description is minimal and lacks operational context.

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?

The description is appropriately sized and front-loaded with the core purpose. The Args and Returns sections are structured, but the 'Returns' sentence could be more concise. Overall, it avoids unnecessary verbosity while maintaining clarity.

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?

Given no annotations, 0% schema coverage, and an output schema (implied by 'Returns'), the description is moderately complete. It covers the basic purpose and parameters but lacks context on device state, measurement specifics, and integration with sibling tools. The output schema handles return values, but operational details are missing.

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 adds meaning by explaining 'channel' as 'Channel to measure' and 'threshold_percent' as 'Threshold percentage for pulse measurement (0-100)', which clarifies the purpose beyond the schema's enum and numeric types. However, it does not detail how threshold affects measurement or channel options, leaving some gaps.

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: 'Measure pulse width at specified threshold.' It specifies the verb ('measure') and resource ('pulse width'), distinguishing it from siblings like measure_frequency or measure_amplitude. However, it does not explicitly differentiate from similar measurement tools beyond the specific measurement type.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context (e.g., after configuring a channel), or exclusions. Given siblings like measure_amplitude and measure_frequency, there is no explicit comparison or usage context provided.

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