Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

evaluate_iso_20816

Analyzes vibration data to determine ISO 20816-3 severity zones for rotating machinery, providing actionable recommendations for maintenance.

Instructions

    Evaluate vibration severity according to ISO 20816-3 standard.

    ISO 20816-3 defines vibration severity zones for rotating machinery based on
    broadband RMS velocity measurements on non-rotating parts (bearings, housings).

    **CRITICAL - LLM Inference Policy:**
    - **NEVER infer fault type or severity from filename** (e.g., "OuterRaceFault_1.csv" does NOT mean outer race fault)
    - **NEVER assume baseline/healthy from filename** (e.g., "baseline" does NOT guarantee Zone A)
    - Treat ALL filenames as opaque identifiers
    - Report ONLY the ISO zone returned by measurement, regardless of filename
    - If filename suggests "baseline" but measurement shows Zone C/D, report Zone C/D

    **DEFAULTS** (use if user doesn't specify):
    - machine_group = 2 (medium-sized machines, most common)
    - support_type = "rigid" (horizontal machines on foundations)

    **Machine Group Selection Guide** (ask user if unsure):
    - Group 1: Large machines (power >300 kW OR shaft height H >= 315 mm)
      Examples: Large turbines, generators, compressors, large pumps
    - Group 2: Medium machines (15-300 kW OR 160mm <= H < 315mm) [DEFAULT]
      Examples: Industrial motors, fans, pumps, gearboxes

    **Support Type Selection Guide** (ask user if unsure):
    - "rigid": Machine on stiff foundation, horizontal orientation [DEFAULT]
      Rule: Lowest natural frequency > 1.25 x main excitation frequency
      Examples: Motors/pumps on concrete, horizontal compressors
    - "flexible": Machine on soft supports, vertical, or large turbine-generator sets
      Examples: Vertical pumps, machines on springs, large turbogenerators

    **When to ask user**:
    - If power/dimensions unknown -> use defaults (Group 2, rigid)
    - If clearly large turbine (>10 MW) -> suggest Group 1, flexible
    - If vertical machine -> suggest flexible
    - If user provides machine specs -> use guide above

    Evaluation Zones:
    - Zone A (Green): New machine condition - excellent
    - Zone B (Yellow): Acceptable for long-term unrestricted operation
    - Zone C (Orange): Unsatisfactory - limited operation, plan maintenance
    - Zone D (Red): Sufficient severity to cause damage - immediate action

    Args:
        signal_file: Name of the CSV file in data/signals/
        sampling_rate: Sampling frequency in Hz (default: 10000)
        machine_group: Machine group 1 (large) or 2 (medium) (default: 2 - medium)
        support_type: 'rigid' or 'flexible' (default: 'rigid')
        operating_speed_rpm: Operating speed in RPM (optional, for frequency range selection)
        signal_unit: Signal unit - 'g' or 'm/s2' (acceleration) or 'mm/s' or 'm/s' (velocity).

                     **PRIORITY ORDER FOR UNIT DETECTION:**
                     1. Check metadata file for 'signal_unit' field (recommended)
                     2. Use this parameter if explicitly provided
                     3. If neither exists: LLM will ask user to confirm based on RMS hypothesis
                     4. Default assumption: 'g' (most common for vibration sensors)

                     **IMPORTANT**: Wrong unit completely invalidates ISO 20816-3 results!
                     Best practice: Add 'signal_unit' field to metadata JSON files.

    Returns:
        ISO20816Result with evaluation zone, severity level, and recommendations

    Example:
        await evaluate_iso_20816(
            ctx,
            "motor_vibration.csv",
            sampling_rate=10000,
            machine_group=2,
            support_type="rigid",
            operating_speed_rpm=1500,
            signal_unit="g"  # Explicitly specify: 'g' or 'mm/s'
        )
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
signal_fileYes
sampling_rateNo
machine_groupNo
support_typeNorigid
operating_speed_rpmNo
signal_unitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rms_velocityYesRMS velocity in mm/s (broadband)
machine_groupYesMachine group (1 or 2)
support_typeYesSupport type: 'rigid' or 'flexible'
zoneYesEvaluation zone: 'A', 'B', 'C', or 'D'
zone_descriptionYesZone description and recommendation
severity_levelYesSeverity level: 'Good', 'Acceptable', 'Unsatisfactory', 'Unacceptable'
color_codeYesColor code: 'green', 'yellow', 'orange', 'red'
boundary_abYesZone A/B boundary (mm/s)
boundary_bcYesZone B/C boundary (mm/s)
boundary_cdYesZone C/D boundary (mm/s)
frequency_rangeYesFrequency range used for measurement
operating_speed_rpmNoOperating speed in RPM
Behavior5/5

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

With no annotations provided, the description carries the full burden, and it thoroughly discloses behavioral traits: it evaluates based on broadband RMS velocity on non-rotating parts, mandates ignoring filenames (critical LLM policy), warns that wrong units invalidate results, and describes the return format (zone, severity, recommendations).

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 lengthy but well-structured with clear sections (LLM policy, defaults, selection guides, args, returns, example). Every section adds value given the complexity of the tool; however, some redundancy could be trimmed (e.g., repeating zone definitions in two places). Still well-organized and front-loaded with purpose.

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?

Given the tool's 6 parameters, complex behavioral rules, and existing output schema, the description is exceptionally complete: it covers all parameters, defaults, user guidance, return structure, and an example. The presence of an output schema reduces the need to detail return values, but the description still mentions them briefly.

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 coverage is 0%, but the description adds full meaning to each parameter: explains signal_file location, defaults and meanings for sampling_rate, machine_group, support_type, operating_speed_rpm, and signal_unit with priority detection rules and warnings. This far exceeds the schema's minimal information.

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 evaluates vibration severity according to ISO 20816-3 standard, using specific verbs ('Evaluate') and resource ('vibration severity'), and distinguishes itself from sibling tools like 'plot_iso_20816_chart' by focusing on the evaluation logic.

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

Usage Guidelines4/5

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

The description provides explicit guidance on when to use defaults, when to ask the user, and includes selection guides for machine groups and support types. However, it does not compare itself to other severity assessment tools (e.g., 'assess_vibration_severity'), which would further clarify when to use this specific tool.

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