Skip to main content
Glama
industrial-aiops

OT-AIops

fleet_incidents

Read-only

Roll up site-level RCA incidents to compute total incidents, affected sites, and top fleet-wide root causes. Read-only, no device I/O.

Instructions

[READ][risk=low] Roll up active RCA incidents across sites → fleet-wide top causes.

Aggregates the incidents each site reports into a fleet picture: how many incidents, which sites
are affected, and the most common root causes across the whole fleet. Read-only; no device I/O.

Args:
    sites: Per-site reports carrying incidents: [{site, incidents:[{cause|primary_cause,
        confidence?}]}].

Returns dict: {total_incidents, sites_with_incidents, affected_sites[], top_causes[]}.

Example: fleet_incidents(sites=[{"site":"plant-sh","incidents":[{"cause":"network"}]}]).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sitesYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true and destructiveHint=false. The description adds value by explicitly stating 'Read-only; no device I/O' and describing the aggregation behavior and return structure. No contradictions with annotations.

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?

The description is front-loaded with a summary tag and then provides structured sections (Args, Returns, Example). It is comprehensive without excessive wordiness. Each sentence contributes useful information.

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?

Given the tool's simplicity (single parameter, no output schema), the description fully covers the purpose, parameter structure, return format, and provides an example. No gaps remain for an agent to use correctly.

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?

The input schema has 0% description coverage, so the description must carry the full burden. It explains the 'sites' parameter as an array of objects with 'site' and 'incidents' fields, detailing the incident structure. This adds meaning beyond the bare schema. A slight deduction for informal formatting.

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 'Roll up' and the resource 'active RCA incidents across sites' to produce 'fleet-wide top causes'. It explains the aggregation purpose well. However, it does not explicitly distinguish this tool from similar sibling tools like 'fleet_status' or 'downtime_root_cause', so a perfect score is not warranted.

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?

The description indicates when to use the tool (to get a fleet overview of RCA incidents) and notes it is read-only with no device I/O. However, it does not mention when not to use it or suggest alternative tools for specific scenarios, leaving some ambiguity.

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'

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