Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

estimate_rul

Estimates remaining useful life by analyzing a degradation signal, extracting features, and fitting a curve to predict when failure threshold will be reached.

Instructions

Estimate Remaining Useful Life from a degradation signal.

    Segments the signal, extracts a feature series (e.g. RMS over time),
    and fits a degradation curve to estimate when *failure_threshold*
    will be reached.

    Args:
        ctx: MCP context for user communication.
        signal_file: CSV signal file in the data directory.
        failure_threshold: Feature value at which the component is
            considered failed.
        method: Estimation method — "linear", "exponential", "weibull",
            or "kalman" (default: "linear").
        feature_name: Time-domain feature to track (default: "rms").
        sampling_interval: Time between successive segments in the
            units you want the RUL expressed in (default: 1.0).
        sampling_rate: Signal sampling rate in Hz (auto-detect if None).
        segment_duration: Duration of each segment in seconds.
        overlap_ratio: Overlap between segments (0-1).

    Returns:
        RULEstimationResult with estimated RUL and confidence.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
signal_fileYes
failure_thresholdYes
methodNolinear
feature_nameNorms
sampling_intervalNo
sampling_rateNo
segment_durationNo
overlap_ratioNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rulYesEstimated remaining useful life in time units
confidenceYesR-squared or confidence metric (0-1)
methodYesEstimation method used
confidence_intervalNo[lower, upper] RUL bounds (Kalman only)
shapeNoWeibull shape parameter (Weibull only)
scaleNoWeibull scale parameter (Weibull only)
estimated_rateNoEstimated degradation rate (Kalman only)
Behavior3/5

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

With no annotations, the description carries full burden. It discloses the algorithm steps and that it returns a result with confidence, but does not mention side effects, permissions, data directory specifics, or error handling. Some behavioral context is provided but incomplete.

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 a single paragraph with a clear Args block and Returns line. It is front-loaded with the main purpose. While it includes some implementation details, it remains concise and well-structured.

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

Completeness4/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 (indicated true), the description adequately covers the return value. It explains all parameters and the process. However, it lacks information about the data directory location and prerequisites, which would improve completeness.

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 the description explains all 8 parameters: signal_file, failure_threshold, method, feature_name, sampling_interval, sampling_rate, segment_duration, overlap_ratio. It adds meaning beyond the schema by describing their purpose and defaults.

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 estimates Remaining Useful Life from a degradation signal, detailing the process of segmentation, feature extraction, and curve fitting. This distinguishes it from sibling tools like analyze_signal_trend or detect_signal_degradation_onset.

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?

The description implies usage for RUL estimation but does not explicitly state when to use or avoid this tool versus alternatives among the many sibling tools. No when-not-to-use or alternative guidance is provided.

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