Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Create Incident

createIncident

Post an active incident banner on a status page to notify users of issues like API degraded. Follow up with updates and resolve the incident when service recovers.

Instructions

Posts an incident banner on a status page, for example "API degraded". It shows on the page at once, pinned and active, alongside any other active incidents. Follow up with updateIncident as things change, and resolveIncident when it is over.

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>",
      "title": "<title>",
      "content": "<content>"
    },
    "name": "createIncident"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe status page slug. Find slugs with listStatusPages.
styleNoBanner color (default: primary). primary, info, warning, danger, light or dark
titleYesHeadline of the banner
contentYesBody of the banner, in Markdown

Output Schema

NameRequiredDescriptionDefault
okYes
incidentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses real behavior: the banner appears immediately, is pinned and active, and coexists with other active incidents. It stops short of stating permission requirements or what happens on repeat calls with identical titles, which matters given idempotentHint=false.

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, no filler, and the core action is front-loaded before the lifecycle follow-ups. Every clause carries either scope, timing, or sequencing 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?

For a four-parameter creation tool with full schema coverage, an output schema, and complete annotations, the description covers what is needed to call it and what to do next. Missing only minor operational details like permission needs or duplicate handling.

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 coverage is 100%, so slug, style, title and content are all already documented with the slug even pointing to listStatusPages. The description adds no parameter-level meaning beyond what the schema provides, so the baseline of 3 applies.

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 ("Posts an incident banner on a status page") plus a concrete example ("API degraded"), which separates it cleanly from updateIncident and resolveIncident named in the same sentence.

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?

Explicitly routes the agent forward in the lifecycle: use updateIncident as things change and resolveIncident when it is over. It gives clear context for this tool's place in the workflow, though it does not spell out prerequisites (e.g., a status page must exist) or when creating an incident is inappropriate.

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