Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

generate_fft_report

Generate an FFT spectrum report from vibration signal data to detect machinery faults. Produces an HTML file with peak detection and harmonic labeling.

Instructions

    Generate professional FFT spectrum report as HTML file.

    **NEW PREFERRED METHOD**: Generates a professional HTML report file
    instead of inline content. Saves to reports/ directory.

    Args:
        signal_file: Signal filename in data/signals/
        sampling_rate: Sampling rate in Hz (auto-detect if None)
        max_freq: Maximum frequency to display (Hz). Default 5000 Hz
        num_peaks: Number of peaks to detect and label. Default 15
        rotation_freq: Optional shaft rotation frequency for harmonic labels
        ctx: MCP context

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

    Example:
        >>> result = generate_fft_report("real_train/baseline_1.csv")
        >>> # User can open: result['file_path']
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
signal_fileYes
sampling_rateNo
max_freqNo
num_peaksNo
rotation_freqNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that output is an HTML file saved to reports/ directory, returns dictionary with file path/metadata/summary (no HTML content), and mentions auto-detect for sampling_rate. Does not cover potential side effects or permissions, but sufficient for basic behavioral understanding.

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 with a clear one-line summary, a highlighted new method, standard Args/Returns sections, and an example. Every sentence adds value. No 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 5 parameters and an output schema, description covers all aspects: purpose, parameter details, return values, and example usage. Output schema further defines the return shape. Fully sufficient for agent to select and invoke correctly.

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 description coverage is 0%, but description compensates fully with detailed parameter explanations: signal_file path, sampling_rate auto-detect, max_freq default 5000 Hz, num_peaks default 15, rotation_freq for harmonic labels. Adds significant meaning beyond the input 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?

Clearly states 'Generate professional FFT spectrum report as HTML file.' The verb and resource are specific. Distinguishes from sibling report tools by specifying 'FFT' and 'HTML file'. The note about 'NEW PREFERRED METHOD' adds context about the output format.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage for FFT spectrum reports, but lacks explicit when-to-use or when-not-to-use guidance compared to sibling report tools like generate_envelope_report or generate_diagnostic_report_docx. No alternatives mentioned.

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