Skip to main content
Glama
markuskreitzer

PicoScope MCP Server

by markuskreitzer
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_streaming_data

Retrieve real-time streaming data from PicoScope oscilloscopes to capture and analyze live signals for measurement and monitoring applications.

Instructions

Get latest streaming data.

Args: max_samples: Maximum number of samples to retrieve.

Returns: Dictionary containing latest streaming data for enabled channels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_samplesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/picoscope_mcp/tools/acquisition.py:162-173 (handler)
    The handler function for the 'get_streaming_data' tool. It is decorated with @mcp.tool(), which registers it with the MCP server. Currently implemented as a stub returning 'not_implemented' status.
    @mcp.tool()
def get_streaming_data(max_samples: int = 1000) -> dict[str, Any]:
    """Get latest streaming data.

    Args:
        max_samples: Maximum number of samples to retrieve.

    Returns:
        Dictionary containing latest streaming data for enabled channels.
    """
    # TODO: Implement streaming data retrieval
    return {"status": "not_implemented", "max_samples": max_samples}
  • src/picoscope_mcp/server.py:16-19 (registration)
    Registration of tool groups in the main server.py file. The call to register_acquisition_tools(mcp) triggers the definition and registration of the get_streaming_data tool.
    register_configuration_tools(mcp)
register_acquisition_tools(mcp)
register_analysis_tools(mcp)
register_advanced_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 mentions retrieving 'latest streaming data' and 'for enabled channels', but lacks details on behavioral traits such as whether this is a read-only operation (implied by 'Get'), potential rate limits, data format, or if it requires an active streaming session. This leaves significant gaps for a tool that likely interacts with real-time data.

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 with a brief purpose statement followed by structured 'Args' and 'Returns' sections. It's front-loaded and efficient, with no wasted sentences, though the 'Returns' section could be more concise by integrating with the purpose statement.

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 the tool's complexity (likely real-time data retrieval), no annotations, and an output schema (implied by 'Returns' statement), the description is minimally adequate. It covers the basic purpose and parameter but lacks context on prerequisites, data format, or error handling, leaving gaps that could hinder effective use by an AI agent.

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 description adds meaning beyond the input schema by explaining that 'max_samples' is the 'Maximum number of samples to retrieve', which clarifies its purpose. With 0% schema description coverage and only one parameter, this compensates well, though it doesn't detail constraints like valid ranges or units. The baseline is high due to low parameter count and coverage.

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

Purpose3/5

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

The description states the tool 'Get latest streaming data' which provides a clear verb ('Get') and resource ('streaming data'), but it's vague about what 'streaming data' entails and doesn't distinguish it from sibling tools like 'get_statistics' or 'export_waveform' that might also retrieve data. It specifies 'for enabled channels' which adds some context but remains general.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites like needing streaming to be active (implied by 'start_streaming' sibling) or when to choose this over tools like 'get_statistics' for processed data. There's no explicit when/when-not usage advice.

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