Utility Matrix

Alert Fatigue Calculator

alert-fatigue-calculator

Read-onlyIdempotent

Use when a user asks about alert noise, alert fatigue, or on-call burden from non-actionable alerts. Given weekly alert volume, actionable %, engineer count, and avg resolution time, returns noise rate, wasted hours, and fatigue tier.

Input Schema

Name	Required	Description
`actionable_pct`	Yes	actionable expressed as a percentage.
`engineer_count`	Yes	engineer count used by this deterministic tool.
`alerts_per_week`	Yes	alerts per week used by this deterministic tool.
`avg_resolution_min`	Yes	avg resolution min used by this deterministic tool.

Output Schema

Name	Required	Description	Default
`next_step`	Yes
`output_tier`	Yes
`signal_value`	Yes
`fatigue_index`	Yes
`next_step_url`	Yes
`remaining_pct`	Yes
`why_follow_up`	Yes
`interpretation`	Yes
`noise_rate_pct`	Yes
`affiliate_context`	No
`computation_basis`	Yes
`annual_wasted_hours`	Yes
`noise_alerts_per_week`	Yes
`wasted_hours_per_week`	Yes
`burden_per_engineer_hours`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 28, 2026
- addedInput schema / properties / actionable_pct / description
```
Added value: +"actionable expressed as a percentage."
```
- addedInput schema / properties / actionable_pct / examples
```
Added value: +[
+  1
+]
```
- addedInput schema / properties / alerts_per_week / description
```
Added value: +"alerts per week used by this deterministic tool."
```
- addedInput schema / properties / alerts_per_week / examples
```
Added value: +[
+  1
+]
```
- addedInput schema / properties / avg_resolution_min / description
```
Added value: +"avg resolution min used by this deterministic tool."
```
- addedInput schema / properties / avg_resolution_min / examples
```
Added value: +[
+  1
+]
```
- addedInput schema / properties / engineer_count / description
```
Added value: +"engineer count used by this deterministic tool."
```
- addedInput schema / properties / engineer_count / examples
```
Added value: +[
+  1
+]
```

Changed1 schema field changedJul 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "affiliate_context": {
+      "additionalProperties": false,
+      "properties": {
+        "affiliate": {
+          "type": "string"
+        },
+        "cta_label": {
+          "type": "string"
+        },
+        "disclosure": {
+          "type": "string"
+        },
+        "framing": {
+          "type": "string"
+        },
+        "posture": {
+          "enum": [
+            "secondary"
+          ],
+          "type": "string"
+        },
+        "slot_id": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        },
+        "variant": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "affiliate",
+        "cta_label",
+        "disclosure",
+        "framing",
+        "posture",
+        "slot_id",
+        "url",
+        "variant"
+      ],
+      "type": "object"
+    },
+    "annual_wasted_hours": {
+      "type": "number"
+    },
+    "burden_per_engineer_hours": {
+      "type": "number"
+    },
+    "computation_basis": {
+      "type": "string"
+    },
+    "fatigue_index": {
+      "type": "number"
+    },
+    "interpretation": {
+      "type": "string"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "next_step_url": {
+      "type": "string"
+    },
+    "noise_alerts_per_week": {
+      "type": "number"
+    },
+    "noise_rate_pct": {
+      "type": "number"
+    },
+    "output_tier": {
+      "type": "string"
+    },
+    "remaining_pct": {
+      "type": "number"
+    },
+    "signal_value": {
+      "type": "number"
+    },
+    "wasted_hours_per_week": {
+      "type": "number"
+    },
+    "why_follow_up": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "annual_wasted_hours",
+    "burden_per_engineer_hours",
+    "computation_basis",
+    "fatigue_index",
+    "interpretation",
+    "next_step",
+    "next_step_url",
+    "noise_alerts_per_week",
+    "noise_rate_pct",
+    "output_tier",
+    "remaining_pct",
+    "signal_value",
+    "wasted_hours_per_week",
+    "why_follow_up"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 13, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedJun 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is low. The description usefully adds that it is a deterministic computation and names the three return values, though an output schema already exists, so that disclosure is largely redundant rather than additive.

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?

Two sentences, front-loaded with the triggering condition followed by inputs and outputs. No filler, no repetition, and the most decision-relevant information leads.

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?

For a simple deterministic calculator with a complete schema, full annotations, and an output schema, the description covers what an agent needs to invoke it correctly. The only omission is guidance on how it relates to the near-identical on-call-burden-calculator sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all four parameters. The description merely restates them (weekly alert volume, actionable %, engineer count, avg resolution time) with no added syntax, units, or edge-case guidance beyond what the schema provides — the expected baseline 3.

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?

States a specific resource (alert fatigue / noise) and spells out both the inputs consumed and outputs produced (noise rate, wasted hours, fatigue tier). However, it does not differentiate itself from its close sibling on-call-burden-calculator, which is a notable gap given it claims 'on-call burden' as a trigger phrase.

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?

The opening 'Use when a user asks about alert noise, alert fatigue, or on-call burden from non-actionable alerts' gives clear triggering context. It stops short of naming exclusions or pointing to the overlapping on-call-burden-calculator, which is exactly the kind of disambiguation this sibling set needs.

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

All Utility Matrix tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?