Skip to main content
Glama
Industrial-AIops Energy

Industrial-AIops Energy

downtime_attribution

Read-only

Ranks stoppages and attributes downstream stops to their declared upstream origin by topology and stop order, separating the true trigger from consequences.

Instructions

[READ][risk=low] Which stoppage started it, and which ones were downstream of it.

RCA weights evidence by TIME alone — a signal before onset counts, one after
counts less. That is the honest half of the axis. Run `downtime_root_cause`
per asset after one upstream stop and every downstream machine comes back
with its own confident local root cause: each internally consistent, each
citing real signals, and all but one about a machine that stopped because it
was starved. The distinguishing fact is not in the evidence — it is the
line's topology.

Two rules decide an attribution and both must hold: the candidate must be
**declared upstream** of the asset, and it must have **stopped first**. An
upstream asset that stopped later cannot have caused an earlier stop, however
upstream it is.

Topology is declared, never inferred (D25). Co-occurrence on a production
line is guaranteed — everything stops together — so mining it for edges would
manufacture the causality this exists to remove. With no relations declared
every row comes back `not_evaluable` and the reason names the command that
fixes it. Assets the topology does not connect are left `unattributed` rather
than folded into the origin's column.

This ranks the stoppages; it does not diagnose the origin. Run
`downtime_root_cause` on the origin asset for that.

Args:
    stoppages: [{asset, start, end?}] for one incident window (ISO-8601).
    site: Which declared line topology to use (default "default").
    max_lead_s: A downstream stop is attributed only if it began within this
        many seconds of the upstream one (default 900).

Returns dict: {site, stoppages_evaluated, relations_declared, max_lead_s,
    verdict ('origin'|'multiple_origins'|'unattributed'|'not_evaluable'),
    origins, consequence_count, attributions:[{asset, start, status,
    origin_asset?, hops_upstream?, lead_s?, explains?, detail}], advisory}.

Example: downtime_attribution(stoppages=[{"asset":"filler","start":"2026-01-05T06:00:00Z"},
    {"asset":"capper","start":"2026-01-05T06:01:00Z"}]).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "stoppages": "<stoppages>"
    },
    "name": "downtime_attribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNodefault
stoppagesYes
max_lead_sNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.13

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark it readOnly and non-destructive, and the description adds substantial behavioral detail beyond that: evidence is weighted by time alone, topology is declared never inferred, co-occurrence is deliberately not mined, unconnected assets are left unattributed, and the tool ranks rather than diagnoses. No contradiction exists between description and annotations.

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 long but earns its length: the motivating RCA example explains why topology matters, the two rules are crisp, and the Args/Returns/Example block is cleanly organized and front-loaded with purpose and risk. No sentence is redundant; the vivid explanatory paragraph clarifies behavior rather than padding.

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?

With no output schema present, the description thoroughly documents the return dict, edge-case statuses like not_evaluable and unattributed, and the exact effect of missing topology declarations. It also gives an example call. This is complete enough for an agent to select and invoke the tool correctly without additional context.

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 the description fully compensates: it defines stoppages as [{asset, start, end?}] for one ISO-8601 incident window, explains site as the declared line topology with default 'default', and specifies max_lead_s as the downstream attribution window with default 900. It also documents the return dictionary structure and provides a concrete example.

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 a clear question that defines the tool's role — identifying which stoppage started an incident and which were downstream — and later states 'This ranks the stoppages; it does not diagnose the origin,' drawing a crisp boundary against downtime_root_cause. It names the specific resource (stoppages) and action (attribution/ranking), making it easy for an agent to distinguish from siblings.

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 explicitly routes between this tool and downtime_root_cause: 'Run downtime_root_cause on the origin asset for that' and explains the failure mode when no relations are declared, including that the reason names the fixing command. It also states both rules that must hold, so an agent knows exactly when a candidate qualifies.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools