Skip to main content
Glama
Sign In

Utility Matrix

by io.github.helphub369
OverviewDiscussionsAdmin

MTTR Calculator

mttr-calculator
Read-onlyIdempotent

Use when a user asks about MTTR or DORA recovery time. Takes incident timestamps (string lines "start,detected,resolved" or array of {start,detected,resolved}).

Input Schema

NameRequiredDescriptionDefault
incidentsYesincidents used by this deterministic tool.

Output Schema

NameRequiredDescriptionDefault
next_stepYes
dora_ratingYes
output_tierYes
mttd_minutesYes
mttr_minutesYes
signal_valueYes
next_step_urlYes
remaining_pctYes
why_follow_upYes
incident_countYes
interpretationYes
affiliate_contextNo
computation_basisYes
mean_total_minutesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / incidents / examples
      Previous value: -[
-  "example"
-]New value: +[
+  "2026-04-01T10:00,2026-04-01T10:05,2026-04-01T10:30"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / incidents / description
      Added value: +"incidents used by this deterministic tool."
    • addedInput schema / properties / incidents / examples
      Added value: +[
+  "example"
+]
  3. Changed1 schema field changed
    • 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"
+    },
+    "computation_basis": {
+      "type": "string"
+    },
+    "dora_rating": {
+      "type": "string"
+    },
+    "incident_count": {
+      "type": "number"
+    },
+    "interpretation": {
+      "type": "string"
+    },
+    "mean_total_minutes": {
+      "type": "number"
+    },
+    "mttd_minutes": {
+      "type": "number"
+    },
+    "mttr_minutes": {
+      "type": "number"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "next_step_url": {
+      "type": "string"
+    },
+    "output_tier": {
+      "type": "string"
+    },
+    "remaining_pct": {
+      "type": "number"
+    },
+    "signal_value": {
+      "type": "number"
+    },
+    "why_follow_up": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "computation_basis",
+    "dora_rating",
+    "incident_count",
+    "interpretation",
+    "mean_total_minutes",
+    "mttd_minutes",
+    "mttr_minutes",
+    "next_step",
+    "next_step_url",
+    "output_tier",
+    "remaining_pct",
+    "signal_value",
+    "why_follow_up"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  5. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds the accepted input shape but says nothing about aggregation across multiple incidents, the recovery-time formula, or error behavior on malformed timestamps.

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?

Two sentences, front-loaded with the usage trigger and followed by the input contract; nothing is wasted. The second sentence is dense but compact, not padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the single required parameter is described. The remaining gap is disambiguation from dora-metrics-calculator and clarification of how the three timestamps map to the reported MTTR, which matters for a metric calculator in this crowded sibling set.

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?

Schema coverage is 100%, but the schema's own parameter text ("incidents used by this deterministic tool.") is uninformative, so the description's specification of the two accepted formats — comma-separated "start,detected,resolved" lines or an array of objects — is genuinely additive. It still leaves the meaning of "detected" versus "start" for the MTTR computation ambiguous.

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 names the metric (MTTR / DORA recovery time) and the input it operates on (incident timestamps), so the verb+resource is identifiable. It does not, however, distinguish itself from the sibling dora-metrics-calculator, which plausibly overlaps on the same metric family.

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?

"Use when a user asks about MTTR or DORA recovery time" gives a clear triggering condition for selection. It stops short of any when-not guidance or explicit routing to alternatives such as dora-metrics-calculator for the full DORA suite.

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

All Utility Matrix toolsInspect
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