Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

extract_features_from_signal

Extract 17 statistical features from vibration signal segments using overlapping windows for machinery health analysis.

Instructions

    Extract time-domain features from signal using sliding window segmentation.

    Segments the signal into overlapping windows and extracts 17 statistical features
    from each segment. Features include: mean, std, RMS, kurtosis, crest factor, entropy, etc.

    Args:
        signal_file: Name of the CSV file in data/signals/
        sampling_rate: Sampling frequency in Hz (auto-detect from metadata if None)
        segment_duration: Duration of each segment in seconds (default: 0.1)
        overlap_ratio: Overlap between segments, 0-1 (default: 0.5 = 50%)
        ctx: MCP context for progress/logging

    Returns:
        FeatureExtractionResult with features matrix and metadata

    Example:
        extract_features_from_signal(
            "healthy_motor.csv",
            sampling_rate=10000,
            segment_duration=0.2,
            overlap_ratio=0.5
        )
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
signal_fileYes
sampling_rateNo
segment_durationNo
overlap_ratioNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
num_segmentsYesNumber of segments extracted
segment_length_samplesYesSamples per segment
segment_duration_sYesDuration of each segment in seconds
overlap_ratioYesOverlap ratio between segments
features_shapeYesShape of feature matrix [num_segments, num_features]
feature_namesYesNames of extracted features
features_previewYesFirst 5 segments features (preview)
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the extraction of 17 features, sliding window segmentation, and returns a FeatureExtractionResult. However, it does not mention whether the tool has side effects, requires authorization, or is read-only. The description is informative but lacks a complete behavioral profile.

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 Args, Returns, and Example sections. It is concise but includes all necessary details. The first sentence is clear and front-loaded. Slight improvement could be made by removing redundant phrasing like 'from signal' since the tool name already implies it.

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 tool (4 parameters, no annotations, output schema present), the description is mostly complete. It explains the segmentation process, features extracted, and return type. It could be enhanced by mentioning that the tool does not modify data, but overall it provides sufficient context.

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?

The schema coverage is 0%, and the description compensates excellently by providing detailed explanations for each parameter: signal_file's location, sampling_rate's auto-detection, segment_duration's default and unit, overlap_ratio's range and default. This adds significant meaning beyond the schema's type and default values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Extract time-domain features from signal using sliding window segmentation,' specifying the verb 'extract,' resource 'time-domain features,' and method. However, it does not explicitly differentiate from sibling tools, though the time-domain focus is implicit given sibling tools like analyze_fft and compute_spectrogram_stft.

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 provides default parameters and an example but does not explicitly state when to use this tool versus alternatives, nor does it mention when not to use it. Usage context is implied by the nature of time-domain feature extraction, but no direct guidance is given.

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