Skip to main content
Glama

postmortem

Read-onlyIdempotent

Generate a blameless postmortem document from incident facts—timeline, impact, detection, contributing factors, and action items—while rejecting action items that lack an owner or due date.

Instructions

Generate a blameless postmortem document from incident facts: timeline, impact, detection, contributing factors and owned action items. Rejects action items without owner and due date.

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": {
      "title": "<title>",
      "severity": "<severity>",
      "startedAt": "<startedAt>",
      "detectedAt": "<detectedAt>",
      "mitigatedAt": "<mitigatedAt>",
      "resolvedAt": "<resolvedAt>",
      "impact": "<impact>",
      "timeline": "<timeline>",
      "contributingFactors": "<contributingFactors>",
      "actionItems": "<actionItems>"
    },
    "name": "postmortem"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
impactYes
severityYes
timelineYes
startedAtYes
detectedAtYes
resolvedAtYes
actionItemsYes
mitigatedAtYes
whatWentWellNo
contributingFactorsYes

Output Schema

NameRequiredDescriptionDefault
kindNo
metricsNo
coverageNo
markdownNo
warningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • removedInput schema / properties / actionItems / items / additionalProperties
      Removed value: -false
    • removedInput schema / properties / timeline / items / additionalProperties
      Removed value: -false
    • changedInput schema / required
      Previous value: -[
      -  "title",
      -  "severity",
      -  "startedAt",
      -  "detectedAt",
      -  "mitigatedAt",
      -  "resolvedAt",
      -  "impact",
      -  "timeline",
      -  "contributingFactors",
      -  "whatWentWell",
      -  "actionItems"
      -]New value: +[
      +  "title",
      +  "severity",
      +  "startedAt",
      +  "detectedAt",
      +  "mitigatedAt",
      +  "resolvedAt",
      +  "impact",
      +  "timeline",
      +  "contributingFactors",
      +  "actionItems"
      +]
  2. First observedv0.4.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds the 'blameless' framing and a rejection rule for action items missing owner/due date, but that rule largely restates what the schema's required fields already enforce, and nothing is said about validation failures or output placement.

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 dense, front-loaded sentences with no filler; the section list and the validation rule both earn their place. Slightly list-like but efficient.

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 no explanation, but with 11 parameters, 10 required, zero schema descriptions and nested array item constraints (timeline min 2, actionItems with kind enum), the description leaves significant gaps – notably the required lifecycle timestamps and severity enum.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, yet it only names a handful of concepts and omits title, severity, the four lifecycle timestamps (startedAt/detectedAt/mitigatedAt/resolvedAt) and whatWentWell entirely. No guidance on timestamp ordering, severity levels, or timeline entry expectations.

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?

States a specific verb and artifact ('Generate a blameless postmortem document') and enumerates the sections produced (timeline, impact, detection, contributing factors, owned action items). This is clearly distinguishable from siblings like runbook, decision_record or failure_rehearsal.

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?

Usage is only implied by the phrase 'from incident facts' – the agent can infer it is for post-incident write-ups, but there is no explicit when-to-use/when-not or pointer to a related tool (e.g. runbook or failure_rehearsal) for adjacent needs.

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