Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

analyze_statistics

Calculate key statistical parameters like RMS, crest factor, kurtosis, and peak-to-peak from a loaded signal to screen for machinery faults in vibration diagnostics.

Instructions

    Calculate statistical parameters of a stored signal for diagnostics.

    Statistical parameters are key indicators for diagnostics:
    - RMS: Effective value, correlated to signal energy
    - Crest Factor: Indicates presence of impulses (high = possible faults)
    - Kurtosis: Measures impulsiveness (excess kurtosis; >0 = non-Gaussian, >3 = strong impulses)
    - Peak-to-Peak: Signal range

    Requires the signal loaded via load_signal() first. Statistical
    parameters are screening indicators, not definitive diagnostics —
    combine with frequency-domain evidence.

    **Signal units:** all values are in the signal's native unit. The unit
    is reported only when DECLARED — load_signal(signal_unit=...) or the
    companion _metadata.json — and never guessed from signal amplitude.
    ISO 20816-3 severity tools refuse to produce a verdict until the unit
    is declared.

    Args:
        signal_id: ID of the stored signal (from load_signal).

    Returns:
        StatisticalResult with all statistical parameters

    Raises:
        ValueError: If the signal_id is not loaded.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
signal_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rmsYesRoot Mean Square (effective value)
meanYesMean value
peakYesPeak value
std_devYesStandard deviation
kurtosisYesKurtosis (measure of impulsiveness)
skewnessYesSkewness (asymmetry)
unit_noteYesUnit declaration status and how to declare the unit for ISO severity assessment
signal_unitNoDeclared signal unit ('g', 'm/s2', 'mm/s', 'm/s') from companion metadata — never guessed from amplitude. None when not declared.
crest_factorYesCrest Factor (Peak/RMS)
peak_to_peakYesPeak-to-peak value
Behavior4/5

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

Describes precondition (load_signal), error handling (ValueError), and unit reporting behavior. Lacks explicit statement about read-only nature but is otherwise transparent.

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?

Well-structured with sections for purpose, parameter meanings, usage condition, unit note, and args/returns/raises. Slightly verbose on unit details, but overall efficient.

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?

Covers purpose, parameters, precondition, return type, error handling, and usage guidance. Output schema exists, so return value details are not needed. Complete for this tool.

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?

Parameter 'signal_id' is explained as 'ID of the stored signal (from load_signal)', adding context beyond the schema. Schema coverage is 0%, so description compensates well.

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?

Clearly states 'Calculate statistical parameters of a stored signal for diagnostics' and lists specific parameters (RMS, Crest Factor, etc.). Distinguishes from sibling frequency-domain and envelope tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly requires signal loaded via load_signal() first, notes that statistical parameters are screening indicators, and advises combining with frequency-domain evidence.

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