Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

detect_signal_degradation_onset

Identify the onset of signal degradation in vibration data by analyzing time-domain features and detecting when they surpass baseline variations, enabling proactive maintenance.

Instructions

Detect whether and where a signal begins to degrade.

    Extracts a feature series from the signal and applies change detection
    to identify the first segment where the feature exceeds baseline
    statistics by *threshold_sigma* standard deviations.

    Args:
        ctx: MCP context for user communication.
        signal_file: CSV signal file in the data directory.
        feature_name: Time-domain feature to monitor (default: "rms").
        threshold_sigma: Number of baseline standard deviations to trigger
            degradation onset (default: 3.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:
        DegradationOnsetResult with onset detection outcome.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
signal_fileYes
feature_nameNorms
threshold_sigmaNo
sampling_rateNo
segment_durationNo
overlap_ratioNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
feature_nameYesFeature analyzed
onset_detectedYesWhether degradation onset was detected
onset_segment_indexNoSegment index where degradation starts
threshold_sigmaYesSigma threshold used for detection
num_segmentsYesTotal number of segments
Behavior4/5

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

No annotations are provided, so the description carries full burden. It transparently describes the algorithm: extracting a feature series and applying change detection with baseline statistics. However, it does not mention whether the tool is read-only or any side effects.

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 a clear purpose sentence followed by a docstring-style explanation. It could be slightly more concise by avoiding repetition of defaults already in schema, but overall it's efficient.

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 complexity of the task and the presence of an output schema, the description provides adequate context about the detection process. It lacks mention of data directory or file format prerequisites, but is largely sufficient.

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 compensates by explaining all parameters: signal_file, feature_name, threshold_sigma, sampling_rate, segment_duration, overlap_ratio, including defaults and units. This adds significant 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 states 'Detect whether and where a signal begins to degrade', which is a specific verb (Detect) and resource (signal degradation onset). It clearly distinguishes from sibling tools like analyze_signal_trend or assess_vibration_severity which address different aspects.

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 explains the tool's mechanism but does not explicitly state when to use this tool versus alternatives. Given many sibling tools, guidance on preferred contexts or exclusions would improve selection accuracy.

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