Skip to main content
Glama
markuskreitzer

PicoScope MCP Server

by markuskreitzer
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

measure_rise_time

Measure signal rise time on PicoScope oscilloscopes by calculating the time between user-defined percentage thresholds on specified channels.

Instructions

Measure signal rise time (10% to 90% by default).

Args: channel: Channel to measure. low_threshold_percent: Lower threshold percentage (0-100). high_threshold_percent: Upper threshold percentage (0-100).

Returns: Dictionary containing rise time in seconds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYes
low_threshold_percentNo
high_threshold_percentNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/picoscope_mcp/tools/analysis.py:98-120 (handler)
    The handler function for the 'measure_rise_time' tool. Defines input parameters (channel, thresholds) and currently returns a 'not_implemented' status with TODO for actual logic.
    @mcp.tool()
def measure_rise_time(
    channel: Literal["A", "B", "C", "D"],
    low_threshold_percent: float = 10.0,
    high_threshold_percent: float = 90.0,
) -> dict[str, Any]:
    """Measure signal rise time (10% to 90% by default).

    Args:
        channel: Channel to measure.
        low_threshold_percent: Lower threshold percentage (0-100).
        high_threshold_percent: Upper threshold percentage (0-100).

    Returns:
        Dictionary containing rise time in seconds.
    """
    # TODO: Implement rise time measurement
    return {
        "status": "not_implemented",
        "channel": channel,
        "low_threshold": low_threshold_percent,
        "high_threshold": high_threshold_percent,
    }
  • src/picoscope_mcp/server.py:18-18 (registration)
    Top-level registration call in the MCP server that includes the measure_rise_time tool via register_analysis_tools.
    register_analysis_tools(mcp)
  • src/picoscope_mcp/server.py:8-8 (registration)
    Import of the registration function for analysis tools, which includes measure_rise_time.
    from .tools.analysis import register_analysis_tools

Tool Definition Quality

A3.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the default thresholds but doesn't describe what happens during measurement (e.g., whether it samples live data, uses buffered data, or requires specific signal characteristics), what errors might occur, or any performance considerations. The description is minimal beyond the basic operation.

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 efficiently structured with a clear opening sentence stating the purpose, followed by well-organized sections for Args and Returns. Every sentence adds value without redundancy, and the information is front-loaded with the core functionality stated first.

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 moderate complexity (3 parameters, no annotations, but with an output schema), the description is reasonably complete. It covers the purpose, parameters, and return value. The output schema exists, so the description doesn't need to detail the return structure. However, it lacks context about when to use the tool and behavioral details, which keeps it from being fully comprehensive.

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?

With 0% schema description coverage, the description compensates well by explaining all three parameters in the Args section. It clarifies that 'channel' selects which channel to measure, and both threshold parameters are percentages (0-100) with their roles (lower/upper). The default values (10% and 90%) are implied in the opening sentence but not explicitly stated in the parameter descriptions.

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 tool's purpose with a specific verb ('measure') and resource ('signal rise time'), including the default measurement range (10% to 90%). It distinguishes itself from sibling tools like 'measure_amplitude' or 'measure_frequency' by focusing specifically on rise time measurement.

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. While it mentions the default thresholds, it doesn't explain when rise time measurement is appropriate compared to other measurement tools (like amplitude or frequency) or what prerequisites might be needed (e.g., whether a signal must be actively streaming or captured 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