Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Update Maintenance Window

updateMaintenanceWindow
DestructiveIdempotent

Update an existing Uptime Kuma maintenance window by changing only the fields you pass; monitor and status page lists are replaced when included.

Instructions

Updates an existing maintenance window. Only the fields you pass change, except monitorIDs and statusPageSlugs, which each replace the whole list. To switch a window on or off use setMaintenanceWindowActive. Find the ID with listMaintenanceWindows.

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": {
      "maintenanceID": "<maintenanceID>"
    },
    "name": "updateMaintenanceWindow"
  }
}

Input Schema

NameRequiredDescriptionDefault
cronNoCron expression for when the window starts, e.g. "30 3 * * *" (03:30 daily), for the cron strategy
titleNoTitle of the maintenance window
strategyNoScheduling strategy (see createMaintenanceWindow)
timezoneNoTimezone the dates and times are in (e.g. "America/New_York", "UTC"). Omit to follow the server timezone.
weekdaysNoDays of week (0=Sunday … 6=Saturday) for recurring-weekday strategy
dateRangeNo[start, end] as local times in the window's timezone, e.g. ["2026-10-08T10:00", "2026-10-08T12:00"]. Required for single; optional bounds for recurring strategies; ignored for manual.
timeRangeNoDaily [{hours, minutes}, {hours, minutes}] start and end. Required for the recurring-* strategies, ignored otherwise.
monitorIDsNoIDs of the monitors this window suppresses. A window with no monitors suppresses nothing. On update this REPLACES the current list; pass [] to detach all.
daysOfMonthNoDays of month (1-31) for recurring-day-of-month strategy
descriptionNoDescription or reason for the maintenance
intervalDayNoInterval in days for recurring-interval strategy
maintenanceIDYesThe ID of the maintenance window to update
durationMinutesNoHow long each window lasts, in minutes, for the cron strategy
statusPageSlugsNoSlugs of the status pages that announce this window while it is in effect. On update this REPLACES the current list; pass [] to remove it from all. Find slugs with listStatusPages.

Output Schema

NameRequiredDescriptionDefault
okYes
msgNo
monitorIDsNo
maintenanceIDYes
statusPageSlugsNo

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?

Annotations already declare this is a non-read-only, destructive, idempotent mutation, so the bar is lower. The description adds the important PATCH contract — only passed fields change except monitorIDs and statusPageSlugs, which replace the entire list — which is behavior no annotation conveys. It stops short of stating permission requirements or what the response contains.

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 waste, with the core patch behavior front-loaded before the alternative-tool routing. Nothing is padding.

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 full schema coverage, the description need not explain return values or per-strategy field requirements. It covers mutation semantics and tool routing; only permission/auth context and the reversibility of list replacement are left implicit.

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 all 14 parameters are already documented, including the REPLACES semantics for monitorIDs and statusPageSlugs. The description's contribution is the cross-field rule that unspecified fields are left untouched, which is useful but largely restates what the schema already says for those two arrays.

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 ("Updates an existing maintenance window") and immediately distinguishes itself from sibling mutations by describing partial-update semantics and naming setMaintenanceWindowActive as the tool for toggling on/off. An agent can tell it apart from createMaintenanceWindow/deleteMaintenanceWindow without reading either schema.

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 explicit routing: use setMaintenanceWindowActive to switch a window on or off, and listMaintenanceWindows to find the ID. It does not explicitly say "do not use this to create a window, use createMaintenanceWindow," but the alternatives for the two most confusable operations are named.

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