Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

generate_fft_report

Generate an interactive FFT spectrum report with automatic peak detection and harmonic labeling from stored vibration signals. Identifies up to 15 peaks and highlights harmonics based on shaft RPM.

Instructions

    Generate an interactive FFT spectrum report (HTML) for a stored signal.

    Saves a self-contained Plotly HTML report (spectrum in dB, automatic
    peak detection, harmonic labels) to the reports/ directory with a
    timestamped filename — consecutive runs produce distinct files.
    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).
        max_freq: Maximum frequency to display (Hz). Default 5000 Hz
        num_peaks: Number of peaks to detect and label. Default 15
        rpm: Optional shaft speed in RPM — peaks at integer multiples
            of rpm/60 Hz are labeled as 1x/2x/... harmonics.
        ctx: MCP context

    Returns:
        Dictionary with file path, metadata, and summary (NO HTML content)

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rpmNo
max_freqNo
num_peaksNo
signal_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, description fully discloses side effects (saves HTML file to reports/ directory, timestamped, consecutive runs produce distinct files), prerequisites, return format (dictionary with file path, metadata, summary), and error conditions (ValueError).

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?

Well-structured docstring: one-line summary, behavior paragraph, Args list, Returns, Raises. Each section is concise and adds value 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?

Complete for a report-generation tool: covers purpose, prerequisites, parameters, behavior (timestamped files), return structure, and error handling. Output schema exists for return values, so description need not detail them.

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?

Schema coverage is 0%, but description's Args section adds full semantic meaning: signal_id is ID from load_signal, max_freq is display max in Hz, num_peaks controls peak labeling, rpm enables harmonic labeling. Explains defaults and behavior beyond schema.

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?

Description clearly states 'Generate an interactive FFT spectrum report (HTML) for a stored signal' with specific verb and resource. Distinguishes from sibling tools like analyze_fft (data) and generate_diagnostic_report_docx (DOCX format).

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?

Explicitly states prerequisite: 'Requires the signal loaded via load_signal() first'. Provides context for when to use (interactive HTML report) but does not explicitly differentiate from alternatives like analyze_fft or generate_envelope_report.

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