Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Update Incident

updateIncident
DestructiveIdempotent

Modify an incident banner on a status page by changing only the fields you pass; set pinned false to hide it without resolving, or use resolveIncident to end the incident.

Instructions

Changes an incident banner. Only the fields you pass change. pinned: false takes it off the page without resolving it; to end an incident use resolveIncident. Find the ID with listIncidents or getStatusPage.

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": {
      "slug": "<slug>",
      "incidentID": "<incidentID>"
    },
    "name": "updateIncident"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe status page slug. Find slugs with listStatusPages.
styleNoBanner color: primary (blue), info, warning (yellow), danger (red), light or dark
titleNoNew headline
pinnedNofalse takes the banner off the page; true puts it back
contentNoNew body, in Markdown
incidentIDYesThe ID of the incident to change

Output Schema

NameRequiredDescriptionDefault
okYes
msgNo
incidentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.4/5.0
Behavior3/5

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

The annotations already declare a destructive, idempotent, non-read-only mutation, and the description's main addition is the PATCH semantics ('Only the fields you pass change'), which is genuinely useful context. However, it never explains the destructive side — that passed fields overwrite existing banner content — nor mentions permissions or whether changes appear immediately. Useful but thinner than the annotations imply is needed.

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?

Three short sentences, zero filler, with the core behavior and partial-update rule front-loaded before the disambiguation and ID lookup hint. Every clause carries operational information.

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 an output schema present and all six parameters documented in the schema, the description covers what an agent needs to invoke it correctly. The remaining gap is behavioral edge context such as permission requirements or whether the banner update is immediately live.

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%, so baseline is 3, but the description adds a semantic distinction the schema does not: pinned:false removes the banner 'without resolving it,' clarifying it is a display toggle rather than an incident end. That meaning materially changes how an agent would set that boolean.

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 ('Changes an incident banner') and immediately distinguishes itself from the nearby resolveIncident sibling, which handles ending incidents. An agent can tell this is a field-level edit, not a create/delete/resolve.

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?

Gives explicit when-not guidance ('to end an incident use resolveIncident') and the prerequisite for locating the target ('Find the ID with listIncidents or getStatusPage'). Both the alternative and the discovery path are named rather than inferred.

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