Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

assess_vibration_severity

Evaluate vibration severity against ISO 10816/20816 standards for stored signals. Classify machinery condition using signal ID, machine class, and axis parameters.

Instructions

Assess vibration severity per ISO 10816/20816 for a stored signal.

    Uses the signal_id pattern (load once, reference by ID).
    Signal unit is read from metadata; defaults to 'g' if unknown.

    Args:
        signal_id: ID of the stored signal.
        machine_class: 'I' (small <15kW), 'II' (medium 15-300kW),
            'III' (large rigid >300kW), 'IV' (large flexible).
        axis: Measurement axis (informational).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
signal_idYes
machine_classNoII
axisNovertical

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
signal_idYesSignal identifier used
rms_velocity_mm_sYesRMS velocity in mm/s
machine_classYesMachine class (I, II, III, or IV)
axisYesMeasurement axis
zoneYesISO zone: A, B, C, or D
zone_descriptionYesZone description
severity_levelYesGood, Acceptable, Unsatisfactory, or Unacceptable
color_codeYesgreen, yellow, orange, or red
boundariesYesZone boundaries {AB, BC, CD} in mm/s
unit_conversion_performedYesWhether acceleration-to-velocity conversion was done
original_unitNoOriginal signal unit before conversion
Behavior3/5

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

With no annotations provided, the description partially carries the burden. It notes that signal unit is read from metadata and defaults to 'g', and that axis is informational. However, it does not disclose whether the tool is read-only or if it modifies any data, which is notable for a severity assessment tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured. It starts with the main purpose, then notes about the signal_id pattern and unit defaults, and ends with parameter details. Every sentence contributes without redundancy.

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 tool has 3 parameters and an output schema exists, the description covers the core functionality, parameter meanings, and behavioral notes. It does not explain output format or error handling, but the output schema likely covers the structure. For a specialized tool, it is mostly complete.

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?

Schema coverage is 0%, so the description must compensate. It explains signal_id as the ID of a stored signal, machine_class with a clear list of options and descriptions, and axis as informational. This adds significant meaning beyond the schema, though axis lacks detailed semantics.

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 it assesses vibration severity per ISO 10816/20816 for a stored signal. It specifies the verb, resource (stored signal), and standard, distinguishing it from sibling tools like analyze_fft or evaluate_iso_20816 by its focus on severity assessment per specific ISO standards.

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 implies prior loading of a signal using the signal_id pattern but does not explicitly state when to use this tool over alternatives like evaluate_iso_20816. It lacks guidance on prerequisites or exclusions, leaving the agent to infer usage context.

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