Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

generate_iso_report

Generate an ISO 20816-3 evaluation report for a stored vibration signal, producing a color-coded severity chart with A-D zones and summary.

Instructions

    Generate an ISO 20816-3 evaluation report (HTML) for a stored signal.

    Saves a self-contained Plotly HTML report (color-coded A-D zone
    chart with the measured RMS marker, boundaries, severity text) to
    the reports/ directory with a timestamped filename. The evaluation
    itself is delegated to assess_severity — requires the signal loaded
    via load_signal() first with sampling rate AND a declared unit
    (units are never guessed).

    Args:
        signal_id: ID of the stored signal (from load_signal).
        machine_group: 1 (large, >300 kW) or 2 (medium, 15-300 kW)
        support_type: 'rigid' or 'flexible'
        rpm: Operating speed in RPM (optional; selects the ISO band's
            lower edge below 600 RPM)
        ctx: MCP context

    Returns:
        Dictionary with file path, metadata, and summary (NO HTML content)

    Raises:
        ValueError: If the signal_id is not loaded, or the stored signal
            has no sampling rate or no declared unit.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rpmNo
signal_idYes
support_typeNorigid
machine_groupNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are present, so the description carries full burden. It discloses that the tool saves a Plotly HTML file to the reports/ directory, returns a dictionary (no HTML content), and raises ValueError for missing prerequisites. This adequately informs the agent of side effects and error conditions.

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 a clear purpose statement followed by implementation details and an args section. It is slightly verbose with details like 'color-coded A-D zone chart', but each sentence adds value. Front-loading is good.

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?

The tool has 4 parameters and an output schema, and the description covers all necessary details: prerequisites, parameter meanings, return value structure, and error conditions. The output schema exists, so return values are partially covered, and the description adds context about the file path and metadata.

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 description coverage is 0%, but the docstring explains each parameter in detail: signal_id as the stored signal ID, machine_group with value meanings, support_type with allowed values, and rpm as optional with behavior below 600 RPM. This fully compensates for the lack of schema descriptions.

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 generates an ISO 20816-3 evaluation report (HTML) for a stored signal, using a specific verb and resource. It distinguishes from sibling report generators like generate_fft_report and generate_envelope_report by specifying the standard and delegation to assess_severity.

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 prerequisites (signal loaded via load_signal with sampling rate and declared unit) and notes delegation to assess_severity. It does not explicitly list alternatives or when-not-to-use, but the context is clear for an agent to infer appropriate usage.

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