Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Set Maintenance Window Active

setMaintenanceWindowActive
Idempotent

Switches a maintenance window on or off to control monitor suppression and scheduling; disable it to resume checks, enable it to start or resume maintenance.

Instructions

Switches a maintenance window off (active: false) or back on (active: true). Off, it stops suppressing its monitors and its schedule stops; on, a manual window starts maintenance immediately and a scheduled one follows its schedule again. It acts on a maintenance window; to stop a monitor's checks use setMonitorActive. 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>",
      "active": "<active>"
    },
    "name": "setMaintenanceWindowActive"
  }
}

Input Schema

NameRequiredDescriptionDefault
activeYesfalse switches the window off, true switches it on
maintenanceIDYesThe ID of the maintenance window to switch

Output Schema

NameRequiredDescriptionDefault
okYes
msgNo
activeYes
maintenanceIDYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint=false, destructiveHint=false, idempotentHint=true), and the description adds real behavioral detail beyond them: turning off stops monitor suppression and halts the schedule; turning on either starts maintenance immediately (manual) or resumes the schedule (scheduled). This is exactly the side-effect context the annotations cannot express.

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 the action and its state mapping, followed by effects and then routing to siblings. Every sentence carries information; the sentence 'It acts on a maintenance window' is slightly redundant but functions as the pivot into the alternative-tool guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter idempotent toggle with an output schema and full annotation coverage, the description supplies everything an agent needs: what it toggles, the effect of each state, how to find the ID, and which sibling to use for the adjacent task.

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% and the schema already defines both parameters, including the true/false meaning of active. The description nonetheless adds meaning by explaining the divergent consequences of active=true for manual versus scheduled windows, which the schema does not convey.

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 (switches) and precise resource (a maintenance window) with the two resulting states spelled out inline. The final sentences explicitly separate it from setMonitorActive, so an agent can distinguish it from sibling toggles such as setMonitorActive and setAPIKeyActive without opening any schema.

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 routing: use this for maintenance windows, use setMonitorActive to stop a monitor's checks instead, and use listMaintenanceWindows to obtain the ID. Both an alternative and a prerequisite-discovery step are named.

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