Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

check_custom_vibration_alert

Compare RMS velocity against custom warning, alarm, and danger thresholds to classify vibration alert levels.

Instructions

Check an RMS velocity value against user-defined thresholds.

    Allows custom alert boundaries instead of ISO 10816 defaults.

    Args:
        ctx: MCP context for user communication.
        rms_velocity: RMS velocity in mm/s.
        warning_threshold: Upper boundary of normal zone (mm/s).
        alarm_threshold: Upper boundary of warning zone (mm/s).
        danger_threshold: Upper boundary of alarm zone (mm/s).

    Returns:
        AlertResult with zone classification and alert level.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rms_velocityYes
warning_thresholdYes
alarm_thresholdYes
danger_thresholdYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
alert_levelYesnone, warning, alarm, or danger
zoneYesISO zone classification (A/B/C/D)
rms_velocityYesInput RMS velocity value
exceeded_thresholdNoThreshold that was exceeded
messageYesHuman-readable alert message
Behavior3/5

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

The description explains the operation: comparing RMS velocity against thresholds and returning zone classification. However, it includes a misleading 'ctx' parameter in the Args section that is not in the input schema, which could confuse the agent. Annotations are absent, so the description carries full burden.

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

Conciseness3/5

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

The description is concise overall but includes the unnecessary 'ctx' parameter in the docstring format. The structure is clear with summary and Args/Returns, but the extraneous element wastes space.

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 no annotations, the description adequately explains the purpose, parameters, and return type. It lacks details on error conditions or zone classification logic, but these may be covered by the output schema. Almost complete for a simple comparison 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?

With 0% schema description coverage, the description adds significant value by explaining each parameter's role (e.g., 'Upper boundary of normal zone'). It specifies units for rms_velocity but not for thresholds, slightly reducing completeness.

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 the tool checks an RMS velocity value against user-defined thresholds, distinguishing it from default ISO 10816 checks. The verb 'check' and resource 'custom vibration alert' are specific, but it could more explicitly differentiate from sibling tools like check_vibration_alert.

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 usage for custom thresholds as opposed to ISO defaults, but it does not explicitly state when to use this tool versus alternatives (e.g., check_vibration_alert). No when-not or alternative names are provided.

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