Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

load_signal

Load vibration signal files into the repository for analysis. Single or batch loading with automatic ID generation and unit declaration for ISO severity assessments.

Instructions

Load one signal — or a batch — into the in-memory repository.

    Once loaded, reference the signal by its signal_id in every analysis,
    diagnosis, report, and prognostics tool (the load -> analyze ->
    diagnose -> report flow uses signal_id as the single handle).

    Batch form: pass a LIST of file paths (e.g. for training sets). The
    batch is fail-fast and atomic — all paths and derived ids are
    validated up front, and on the first problem ONE error names the
    offending entries and nothing is loaded. One declared sampling_rate/
    signal_unit applies to all files; per-file metadata wins only when
    the parameter is omitted. Custom signal_id is not allowed for a
    batch (ids derive from each file's relative path).

    signal_id default: the path relative to data/signals/ with separators
    replaced by underscores — 'real_train/baseline_1.csv' loads as
    'real_train_baseline_1', so same-named files in different folders
    never collide silently. Re-loading a path whose id already exists is
    an explicit error unless overwrite=True.

    Signal unit discipline: ISO 20816-3 severity verdicts require a
    DECLARED unit — either via this parameter or a 'signal_unit' field in
    the companion _metadata.json (explicit parameter wins). Units are
    never guessed from signal amplitude; without a declared unit the ISO
    severity block is refused with a structured reason and remedy.

    Args:
        filepath: Filename relative to data/signals/ or absolute path —
            or a list of such paths for an atomic batch load.
        signal_id: Custom ID (single-file loads only; default derives
            from the relative path).
        sampling_rate: Sampling rate in Hz (overrides metadata file).
        signal_unit: Declared signal unit — 'g' or 'm/s2' (acceleration),
            'mm/s' or 'm/s' (velocity). Overrides the metadata file.
        overwrite: Replace existing entries on signal_id collision
            instead of raising.

    Returns:
        StoredSignalInfo for a single load; a list of StoredSignalInfo
        (input order) for a batch.

    Raises:
        ValueError: If signal_unit is invalid, the signal data cannot be
            loaded, a signal_id collides without overwrite=True, or a
            batch contains any invalid entry (nothing is loaded).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filepathYes
overwriteNo
signal_idNo
signal_unitNo
sampling_rateNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Fully discloses behavior: batch atomicity, fail-fast, default signal_id derivation, overwrite semantics, unit discipline (no guessing), and error conditions. No annotations, so description carries full burden and meets it.

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?

Well-structured with paragraphs and bullet-like args. Front-loaded with purpose. Slightly long but each sentence adds value for a complex tool. Could trim some redundancy.

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?

Covers all aspects: return type (StoredSignalInfo), errors (ValueError), preconditions (unit for ISO), and batch/single behavior. With an output schema and high complexity, the description is fully complete.

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 description explains all 5 parameters in detail: filepath (single/list), signal_id (custom or default), sampling_rate, signal_unit (enumerated values), overwrite. Adds restrictions and defaults beyond schema.

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: 'Load one signal — or a batch — into the in-memory repository.' It explains the load-analyze-diagnose-report flow and distinguishes from sibling analysis tools by being the loading step.

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?

Explicitly says to use this before analysis tools, describes batch use for training sets, and warns about unit declaration needed for ISO severity. Provides when-to-use and implications of not following guidelines.

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