Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

plot_signal

Generate interactive time-domain plots to inspect signal quality, identify anomalies, and visualize transients from stored vibration data.

Instructions

    Generate interactive time-domain plot for a stored signal.

    Creates an interactive HTML plot showing the signal in the time domain.
    Useful for inspecting signal quality, identifying anomalies, and
    visualizing transients. Requires the signal loaded via load_signal()
    first; the sampling rate comes from the stored signal metadata.

    Args:
        signal_id: ID of the stored signal (from load_signal).
        time_range: [start_time, end_time] in seconds to zoom on a portion (optional)
        show_statistics: Show RMS, peak levels as horizontal lines (default: True)
        title: Custom plot title (optional)
        ctx: MCP context for progress/logging

    Returns:
        Path to generated HTML file

    Raises:
        ValueError: If the signal_id is not loaded, or the stored signal
            has no sampling rate.

    Example:
        plot_signal(
            "bearing_signal",
            time_range=[0.1, 0.3],  # Zoom on 100-300 ms
            show_statistics=True
        )
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
signal_idYes
time_rangeNo
show_statisticsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: it creates an interactive HTML plot, returns a file path, and raises ValueError for missing signal_id or missing sampling rate. It also explains optional parameters like time_range for zooming and show_statistics for annotation lines, ensuring the agent understands all traits.

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 well-organized with a one-line summary, explanatory paragraph, structured Args/Returns/Raises/Example sections, and every sentence adds value. It is front-loaded with the primary purpose and remains concise without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description sufficiently covers returns (path to HTML file), prerequisites, error conditions, and parameter usage. It provides complete context for a plotting tool without omissions.

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

Parameters5/5

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

Despite the context indicating 0% schema description coverage, the description provides detailed parameter descriptions in an 'Args' section: time_range as [start, end] in seconds for zooming, show_statistics as rendering RMS/peak lines, and title as custom label. This adds substantial meaning beyond the schema's type-only definitions.

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 opens with a clear verb-object phrase 'Generate interactive time-domain plot for a stored signal' and elaborates on use cases like inspecting signal quality and identifying anomalies, effectively distinguishing it from sibling tools such as analyze_fft or compute_spectrogram_stft.

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 explicitly states the prerequisite 'Requires the signal loaded via load_signal() first' and explains when the tool is useful, but does not exclude specific scenarios or mention alternative tools for frequency-domain analysis.

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/LGDiMaggio/predictive-maintenance-mcp'

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