Skip to main content
Glama
industrial-aiops

OT-AIops Energy

pdm_forecast

Read-only

Forecast a series trend and compute ETA to warn/alarm limits, with degradation pattern and remaining useful life for predictive maintenance.

Instructions

[READ][risk=low] Forecast a value's trend + time until it crosses a warn/alarm limit.

The predictive step above baseline_check (which flags a violation that already happened): fits a
robust Theil-Sen trend to the recent history and, if it continues, estimates the ETA to the
nearest limit in the direction of travel — the early warning that makes maintenance predictive
(inverter/turbine degradation, bearing drift, filter clogging). Refuses thin history; read-only,
pure over the provided series; no device I/O.

Beyond the trend, the result deepens into three explainable, stdlib-only views: a degradation
'pattern' (gradual vs sudden vs cyclic), a remaining-useful-life 'rul' block when degrading
(linear + exponential extrapolation to the limit, a confidence band from the slope spread, and a
fit R^2), and optional time-domain 'waveform' features (RMS/kurtosis/crest/... for
vibration-type signals). Each states its own uncertainty rather than guessing.

Args:
    series: Time-ordered samples: [{value, timestamp?}] (timestamp ISO-8601; if all present the
        ETA is in seconds, otherwise in samples). >= 30 numeric samples required.
    warn_high/alarm_high/warn_low/alarm_low: Optional limits; the forecast targets the nearest
        one in the trend's direction (rising → highs, falling → lows).
    imminent_within_s: ETA (seconds) at/under which status is 'imminent' (default 86400 = 24h).
    include_waveform: Add the time-domain 'waveform' feature block (default True). Set False for
        slow trend-only signals where vibration features do not apply.

Returns dict: {status (insufficient_data|stable|degrading|imminent), samples, direction,
    slope_per_unit, unit (s|samples), current, limit:{name,value}, eta_to_limit,
    degradation:{pattern,confidence,rationale,metrics},
    waveform:{rms,crest_factor,kurtosis,...} (when include_waveform),
    rul:{linear,exponential,eta_band,recommended_model,confidence,...} (when degrading)}.

Example: pdm_forecast(series=[{"value": 62.1, "timestamp": "2026-07-12T00:00:00Z"}, ...],
    warn_high=75, alarm_high=85).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seriesYes
warn_lowNo
alarm_lowNo
warn_highNo
alarm_highNo
include_waveformNo
imminent_within_sNo
Behavior5/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with '[READ][risk=low]', 'read-only', 'pure over the provided series', and 'no device I/O'. It also discloses behavioral details beyond annotations: robust Theil-Sen fitting, refusal of thin history, timestamp-dependent ETA units, and structured uncertainty reporting. No contradictions found.

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 well-structured and front-loaded with a one-sentence summary and risk/read indicator, followed by a contextual paragraph, Args, Returns, and an Example. The length is justified by the tool's complexity (7 parameters, multiple output blocks, edge cases), and every section adds distinct value without 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?

This is a complex forecasting tool with no output schema, so the description must compensate by explaining input requirements, behavioral constraints, and return structure. It does so comprehensively: return dict fields, degradation/rule/waveform sub-blocks, example call, and edge cases like thin history. The description is fully self-sufficient for correct invocation and interpretation.

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?

The input schema provides zero description coverage (0%), so the description bears full responsibility for explaining parameters. It does so thoroughly: series format and minimum length, limit directionality, imminent_within_s default, and include_waveform semantics. Each parameter is given meaningful context that the schema alone cannot convey.

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 states a specific action: forecasting a value's trend and time until it crosses a warn/alarm limit. It explicitly distinguishes itself from sibling baseline_check by positioning itself as the predictive step above that violation-flagging tool. The scope (trend extrapolation, ETA estimation) is concrete and unambiguous.

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?

The description clearly states when to use this tool (predictive early warning before a limit is crossed) versus baseline_check (which flags violations that already happened). It also provides practical usage conditions: requires >=30 samples, refuses thin history, and notes when to disable waveform features (slow trend-only signals). This is explicit, actionable guidance.

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/industrial-aiops/industrial-aiops-energy'

If you have feedback or need assistance with the MCP directory API, please join our Discord server