Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

predict_anomalies

Analyze vibration signals to predict anomalies and assess equipment health using a trained model. Applies complete preprocessing pipeline for accurate diagnostics.

Instructions

    Predict anomalies in new signal using trained model.

    Applies the complete pipeline:
    1. Segment signal
    2. Extract features
    3. Apply scaler (from training)
    4. Apply PCA (from training)
    5. Predict with trained model
    6. Calculate anomaly ratio and overall health

    Args:
        signal_file: Name of CSV file to analyze
        model_name: Name of trained model (default: 'anomaly_model')
        ctx: MCP context for progress/logging

    Returns:
        AnomalyPredictionResult with predictions and health assessment
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
signal_fileYes
model_nameNoanomaly_model

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
num_segmentsYesNumber of segments analyzed
anomaly_countYesNumber of anomalies detected
anomaly_ratioYesRatio of anomalies (0-1)
predictionsYesPredictions per segment: 1=normal, -1=anomaly
anomaly_scoresNoAnomaly scores if available
overall_healthYesOverall health status: 'Healthy', 'Suspicious', 'Faulty'
confidenceYesConfidence level: 'High', 'Medium', 'Low'
Behavior4/5

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

Without annotations, the description provides a detailed step-by-step pipeline of the prediction process, including segmentation, feature extraction, scaling, PCA, prediction, and health assessment. This transparency is sufficient for understanding the tool's behavior.

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 concise and well-structured, starting with the main purpose followed by a clear bullet list of steps. It is appropriately sized and front-loaded, with each sentence adding value.

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 complexity of the ML pipeline, the description explains the steps well and an output schema exists for return values. However, it omits critical constraints like the requirement for a pre-existing model and signal file location, leaving gaps for an agent to infer.

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 schema has 0% description coverage, but the description adds meaning by specifying 'signal_file' as a CSV file for analysis and 'model_name' with a default value. This significantly helps the agent understand parameter purposes, though more details about the CSV format would improve.

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 the tool predicts anomalies in new signals using a trained model, listing a specific 6-step pipeline. It effectively distinguishes from its sibling 'train_anomaly_model' (training vs. prediction) and other analysis tools.

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 lacks explicit guidance on when to use this tool versus alternatives, such as prerequisites like the existence of a trained model or the appropriate format of the signal file. There is no mention of when not to use it.

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