Skip to main content
Glama
industrial-aiops

OT-AIops Energy

oee_multidim

Read-only

Aggregate OEE and energy metrics across shifts, machines, or parts. Identify worst performers and flag energy baseline deviations using tolerance and robust outlier rules.

Instructions

[READ][risk=low] Aggregate OEE (+ optional energy) across dimensions.

Args:
    records: Labelled records — {<dimension labels>, planned_time_s, run_time_s,
        ideal_cycle_time_s, total_count, good_count} plus optional actual_kwh /
        baseline_kwh to enable the energy rollup.
    dimensions: Dimension keys to group by (default ['machine','part','shift']);
        use ['shift'] for the classic by-shift energy comparison.
    emission_factor_kg_per_kwh: Optional carbon factor (kg CO2e/kWh); default is a
        flagged placeholder — pass the grid's published value.
    energy_tolerance: ± band (fraction) for the actual-vs-baseline verdict.

Returns dict: {dimensions, group_count, mean_oee, worst_performers:[...],
    matrix:[{dimensions, oee, oee_pct, availability, performance, quality,
    energy?}]}. When any record carries energy, adds an ``energy_baseline`` block
    that flags cross-group deviation anomalies (tolerance + robust-outlier rules).

Example: oee_multidim(records=[{"shift":"day","planned_time_s":28800,
    "run_time_s":25000,"ideal_cycle_time_s":2,"total_count":12000,
    "good_count":11800,"actual_kwh":940,"baseline_kwh":880}], dimensions=["shift"]).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recordsYes
dimensionsNo
energy_toleranceNo
emission_factor_kg_per_kwhNo
Behavior5/5

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

The description adds behavioral details beyond annotations: it explains that energy data triggers an energy_baseline block with anomaly flagging, notes the emission factor placeholder requires user action, and describes the return dict contents. Given annotations already declare safety, this is rich additional context.

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 with purpose, args, returns, and example. Front-loaded core action, uses bullets for readability, and no wasted sentences.

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?

For a tool with no output schema, the description thoroughly explains the return format, including conditional energy_baseline, and provides an illustrative example. Combined with parameter details, an agent has sufficient information to invoke it correctly.

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%, so the description fully documents all four parameters with meanings, defaults, and expectations. It even specifies the record structure including required fields and optional energy fields.

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 opens with 'Aggregate OEE (+ optional energy) across dimensions', a specific verb-resource pair. It explains return structure and gives an example, distinguishing it from single-point OEE tools like oee_compute (which appears in siblings).

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?

It clearly specifies that dimensions can be passed, with a default of ['machine','part','shift'], and explicitly suggests using ['shift'] for by-shift energy comparison, giving use-case context. However, it doesn't explicitly name alternative tools or state when not to use it.

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