Skip to main content
Glama

Write or publish a post-mortem

write_postmortem
Idempotent

Writes a resolved incident's post-mortem: summary, impact, root cause and follow-ups (one per line), on Pro plans. It stays in the workspace until published: true shows it under the incident on the status pages that show it and in their feeds; false takes it off. Publish only when the user asks. Free.

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": {
      "incident_id": "<incident_id>"
    },
    "name": "write_postmortem"
  }
}

Input Schema

NameRequiredDescriptionDefault
impactNoWho and what was affected, and for how long.
summaryNoWhat happened, in a few sentences.
publishedNotrue shows the post-mortem on the status pages that show the incident; false takes it off. Leave out to keep it as it is.
follow_upsNoWhat will be done so it does not happen again, one per line.
root_causeNoWhat caused the incident.
incident_idYesIncident ID from list_incidents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / follow_ups / description
      Previous value: -"One per line."New value: +"What will be done so it does not happen again, one per line."
    • addedInput schema / properties / impact / description
      Added value: +"Who and what was affected, and for how long."
    • addedInput schema / properties / published / description
      Added value: +"true shows the post-mortem on the status pages that show the incident; false takes it off. Leave out to keep it as it is."
    • addedInput schema / properties / root_cause / description
      Added value: +"What caused the incident."
    • addedInput schema / properties / summary / description
      Added value: +"What happened, in a few sentences."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the key risk: the post-mortem stays internal until published:true makes it visible on public status pages and their feeds, and false retracts it. The 'Publish only when the user asks' caution plus the plan requirement are exactly the behavioral context an agent needs before touching externally visible state; only the word 'Free' is left unexplained.

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?

Front-loaded with purpose and content fields, followed by two short directives. The middle sentence is a long semicolon-chained run-on about publish state that could be split, and the trailing 'Free' is cryptic.

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?

With no output schema but full parameter coverage and strong annotations, the description covers purpose, preconditions, draft vs. published state, and the publish caution. It omits what the call returns and what happens on non-Pro plans, both minor given the structured data already supplied.

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 baseline is 3. The description mostly restates the schema (it repeats the 'one per line' convention and the published true/false semantics almost verbatim), adding no format, length, or interaction details the schema lacks.

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 resource ('Writes a resolved incident's post-mortem') and enumerates the content it carries (summary, impact, root cause, follow-ups). Combined with the plan gate ('Pro plans') and the resolved-incident precondition, an agent knows exactly what this creates and under what conditions.

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?

Gives concrete preconditions ('resolved incident', 'Pro plans') and an explicit when-not instruction ('Publish only when the user asks'). It does not point to an alternative tool, but no sibling covers post-mortems, so the omission costs little.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources