Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

analyze_fft

Convert vibration signals from time to frequency domain to identify harmonic components and detect machinery faults at specific frequencies.

Instructions

    Perform FFT (Fast Fourier Transform) analysis on a signal.

    FFT analysis converts the signal from time domain to frequency domain,
    allowing identification of harmonic components and faults that manifest
    at specific frequencies.

    By default, analyzes a RANDOM 1.0-second segment from the signal for efficiency.
    Set segment_duration=None to analyze the entire signal.

    **CRITICAL - LLM Inference Policy:**
    - **NEVER infer fault type from filename** (e.g., "OuterRaceFault_1.csv" does NOT mean outer race fault exists)
    - **NEVER assume signal characteristics from filename** (e.g., "baseline" does NOT mean healthy)
    - Treat ALL filenames as opaque identifiers
    - Base analysis ONLY on frequency spectrum data returned by this tool
    - If filename suggests a characteristic but data shows otherwise, report the data findings

    **CRITICAL - Parameter Validation:**
    - Sampling rate is auto-detected from metadata if available
    - If no metadata: user MUST provide sampling_rate or results will be UNRELIABLE
    - Segment duration defaults to 1.0s but can be customized
    - User will be notified of all assumptions before analysis proceeds

    Args:
        ctx: MCP context for user communication
        filename: Name of the file containing the signal
        sampling_rate: Sampling frequency in Hz (auto-detect from metadata if None)
        max_frequency: Maximum frequency to analyze (default: Nyquist frequency)
        segment_duration: Duration in seconds to analyze (default: 1.0s random segment).
                         Set to None to analyze full signal.
        random_seed: Random seed for reproducible segment selection (default: None = random)

    Returns:
        FFTResult with frequencies, magnitudes and dominant peak
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes
sampling_rateNo
max_frequencyNo
segment_durationNo
random_seedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
top_peaksYesTop spectral peaks sorted by magnitude
peak_frequencyYesDominant peak frequency (Hz)
peak_magnitudeYesDominant peak magnitude
rms_spectralYesRMS of the magnitude spectrum
total_binsYesTotal number of FFT bins computed
freq_range_hzYes[min_freq, max_freq] of the spectrum
sampling_rateYesSampling frequency (Hz)
num_samplesYesNumber of analyzed samples
frequency_resolutionYesFrequency resolution (Hz)
Behavior4/5

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

Without annotations, the description fully discloses defaults, auto-detection of sampling rate, and the policy against filename-based inference. It tells the agent that assumptions will be communicated to the user. This adds significant behavioral context beyond the schema.

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 well-structured with sections and front-loaded with purpose. However, it is somewhat lengthy due to the inclusion of critical policy and parameter details that could be integrated more succinctly.

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 (FFTResult), the description does not need to cover return values. It fully explains input parameters, default behavior, and usage context. No gaps are identified for this analysis tool.

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 0% schema description coverage, the description thoroughly explains each parameter: filename is required, sampling_rate is auto-detected if None (otherwise unreliable), max_frequency defaults to Nyquist, segment_duration defaults to 1.0s for efficiency (None for full signal), and random_seed enables reproducibility. This adds essential meaning beyond the 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?

The description clearly states it performs FFT analysis on a signal, explains the conversion from time to frequency domain, and identifies harmonic components and faults. This is specific and distinguishes it from sibling tools like analyze_envelope or compute_power_spectral_density.

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?

Provides clear context on default behavior (random 1.0-second segment), how to analyze full signal (set segment_duration=None), and critical policy about not inferring from filenames. It also warns about sampling rate requirements. However, it does not explicitly name alternative tools or scenarios where this tool should be avoided.

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