Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

analyze_statistics

Calculate statistical parameters from vibration signals to identify possible machinery faults. RMS, crest factor, kurtosis, and peak-to-peak values indicate signal energy and impulsiveness.

Instructions

    Calculate statistical parameters of the 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

    **CRITICAL - LLM Inference Policy:**
    - **NEVER infer fault type from filename** (e.g., "OuterRaceFault_1.csv" does NOT mean outer race fault exists)
    - **NEVER assume signal characteristics from filename** (e.g., "baseline" does NOT mean healthy)
    - Treat ALL filenames as opaque identifiers
    - Statistical parameters (RMS/CF/Kurtosis) are indicators ONLY - NOT definitive diagnostics
    - High kurtosis indicates "possible fault" - NOT "confirmed fault"
    - Must be combined with frequency-domain evidence for diagnosis

    Args:
        filename: Name of the file containing the signal

    Returns:
        StatisticalResult with all statistical parameters
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rmsYesRoot Mean Square (effective value)
peak_to_peakYesPeak-to-peak value
peakYesPeak value
crest_factorYesCrest Factor (Peak/RMS)
kurtosisYesKurtosis (measure of impulsiveness)
skewnessYesSkewness (asymmetry)
meanYesMean value
std_devYesStandard deviation
detected_unitYesAuto-detected signal unit (g acceleration or mm/s velocity)
unit_noteYesImportant note about signal units and conversion requirements
Behavior4/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 of behavioral disclosure. It explains the statistical parameters and their meaning, and warns against over-interpretation. However, it does not explicitly state whether the tool is read-only, modifies data, or requires the signal to be loaded first. A score of 4 is appropriate as it adds substantial context but misses some behavioral details.

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 clear sections and bullet points, and the purpose is front-loaded. However, the inclusion of the lengthy 'CRITICAL' policy, while valuable, makes it slightly verbose. A score of 4 reflects minor redundancy but overall good organization.

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?

Despite having only one parameter and an output schema, the description adds comprehensive context: it explains the meaning of each statistical parameter and provides a strict usage policy to prevent misinterpretation. This makes the tool's behavior and limitations fully clear to an agent.

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 has 0% description coverage for the single parameter 'filename', but the description compensates by clarifying: 'Name of the file containing the signal'. Additionally, the policy section provides critical semantics like treating filenames as opaque identifiers, which adds significant value beyond the schema's bare specification.

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's purpose: 'Calculate statistical parameters of the signal for diagnostics.' It lists specific statistical parameters (RMS, Crest Factor, Kurtosis, Peak-to-Peak) and differentiates from sibling tools like analyze_fft and analyze_envelope by focusing on time-domain statistical indicators, making it easy for an agent to select the correct tool.

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?

The description includes a 'CRITICAL - LLM Inference Policy' that explicitly tells the agent when not to infer fault types from filenames and states that statistical parameters are indicators only, not definitive diagnostics. It also recommends combining with frequency-domain evidence, providing excellent guidance on usage context and avoiding misuse.

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