Skip to main content
Glama
devhelmhq

DevHelm MCP Server

Official
by devhelmhq
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

update_status_page_incident

Update incident details on a status page—change title, impact, status, or affected components. Resolve communication gaps by keeping stakeholders informed in real time.

Instructions

Update a status page incident's title, impact, status, or components.

Schedule fields belong on update_status_page_maintenance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesUpdate body for an incident (no schedule fields).
page_idYes
incident_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

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

  1. Changed9 schema fields changedv1.7.0
    • addedInput schema / properties / body / description
      Added value: +"Update body for an incident (no schedule fields)."
    • changedInput schema / properties / body / properties / affectedComponents / anyOf
      Previous value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "componentId": {
-          "description": "Status page component ID",
-          "format": "uuid",
-          "type": "string"
-        },
-        "status": {
-          "description": "Component status during this incident",
-          "enum": [
-            "OPERATIONAL",
-            "DEGRADED_PERFORMANCE",
-            "PARTIAL_OUTAGE",
-            "MAJOR_OUTAGE",
-            "UNDER_MAINTENANCE"
-          ],
-          "type": "string"
-        }
-      },
-      "required": [
-        "componentId",
-        "status"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / body / properties / affectedComponents / description
      Previous value: -"Updated affected components; null preserves current"New value: +"Updated affected components; omit to preserve current"
    • changedInput schema / properties / body / properties / impact / description
      Previous value: -"New impact level; null preserves current"New value: +"New impact; omit to preserve current"
    • removedInput schema / properties / body / properties / postmortemBody
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Postmortem body in markdown; empty string clears"
-}
    • removedInput schema / properties / body / properties / postmortemUrl
      Removed value: -{
-  "anyOf": [
-    {
-      "maxLength": 2048,
-      "minLength": 0,
-      "pattern": "^https?://.*",
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "URL to an external postmortem document; empty string clears"
-}
    • changedInput schema / properties / body / properties / status / description
      Previous value: -"New status; null preserves current"New value: +"New status; omit to preserve current"
    • changedInput schema / properties / body / properties / title / anyOf
      Previous value: -[
-  {
-    "maxLength": 500,
-    "minLength": 0,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 500,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / body / properties / title / description
      Previous value: -"New title; null preserves current"New value: +"New title; omit to preserve current"
  2. First observedv1.0.2

TDQS

A3.9/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It does not mention side effects such as whether status/impact changes trigger notifications, whether the operation is reversible, or what permissions are required. It mostly restates the mutate action and lists the updatable fields.

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 main action and a targeted cross-reference to the maintenance tool. No wasted words and no repetition of schema details.

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?

The description covers the core operation and the most important exclusion well, and the output schema handles return-value expectations. However, as a mutation tool with no annotations, it omits behavioral context like side effects, and it does not address related incident siblings such as post_status_page_incident_update.

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?

The description usefully enumerates the relevant body fields (title, impact, status, components) and adds the 'no schedule fields' exclusion. However, schema coverage is only 33%, and the description does little to clarify page_id/incident_id or the structure of affectedComponents beyond what the schema already provides.

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?

The description uses a specific verb and resource: 'Update a status page incident's title, impact, status, or components.' It clearly identifies what the operation does and immediately distinguishes itself from maintenance updates by stating schedule fields belong on update_status_page_maintenance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when to use this tool: to update incident fields. It also gives a clear when-not rule by routing schedule fields to update_status_page_maintenance, which prevents confusion with the closely related maintenance tool. This gives an agent a practical decision rule.

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/devhelmhq/mcp-server'

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