Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

compute_spectrogram_stft

Computes time-frequency spectrogram from stored signal to detect transient faults and speed changes in vibration data.

Instructions

Compute STFT spectrogram for a stored signal.

    Returns time-frequency summary (no full 2D array). Use for detecting
    time-varying frequency content (transient faults, speed changes).

    Args:
        signal_id: ID of the stored signal.
        nperseg: Samples per STFT segment (default 256).
        noverlap: Overlap between segments (default 128).
        window: Window function (default 'hann').
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
signal_idYes
npersegNo
noverlapNo
windowNohann

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
signal_idYesSignal identifier used
num_samplesYesNumber of samples analyzed
sampling_rateYesSampling rate (Hz)
npersegYesSamples per segment
noverlapYesOverlap between segments
windowYesWindow function used
num_time_binsYesNumber of time bins
num_freq_binsYesNumber of frequency bins
freq_range_hzYes[min_freq, max_freq]
time_range_sYes[start_time, end_time]
max_power_freq_hzYesFrequency with maximum power
max_power_time_sYesTime of maximum power
energy_per_bandYesEnergy in predefined frequency bands
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It indicates the tool computes a spectrogram and returns a summary, but fails to disclose side effects (e.g., is it read-only?), permissions, or any constraints. This is a significant gap for a computational 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 succinct and front-loaded: first line states purpose, followed by a returns note and bullet-point parameter list. Every sentence is necessary and no information is redundant.

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 output schema exists, explicit return value details are not needed. The description mentions the return type and explains parameters. It could benefit from more context on how this tool fits among siblings, but for a simple computational tool it is largely 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 description coverage is 0%, but the description explains each parameter's meaning and default values clearly. It lacks validation details (e.g., allowed window types) but covers the core semantics adequately.

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 verb 'Compute' and resource 'STFT spectrogram for a stored signal', and specifies the output as a 'time-frequency summary'. It implies differentiation from siblings by mentioning transient faults, but does not explicitly name alternatives.

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?

Provides clear context for use: 'detecting time-varying frequency content (transient faults, speed changes)'. However, it offers no guidance on when not to use this tool or what alternatives exist among the many spectral siblings.

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