Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Set Monitor Active

setMonitorActive
Idempotent

Pauses or resumes a monitor by ID, stopping checks and alerts while preserving configuration and history, or restarting checks immediately.

Instructions

Pauses (active: false) or resumes (active: true) a monitor. A paused monitor stops checking, recording heartbeats and alerting; its configuration and history are kept, and resuming restarts checks at once. Setting the state it already has changes nothing. For planned downtime on a schedule use createMaintenanceWindow instead; setMaintenanceWindowActive acts on a maintenance window, not a monitor. Find the ID with listMonitors.

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": {
      "monitorID": "<monitorID>",
      "active": "<active>"
    },
    "name": "setMonitorActive"
  }
}

Input Schema

NameRequiredDescriptionDefault
activeYesfalse pauses the monitor, true resumes it
monitorIDYesThe ID of the monitor to pause or resume

Output Schema

NameRequiredDescriptionDefault
okYes
msgNo
activeYes
monitorIDYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare non-read-only, idempotent, non-destructive behavior, so the bar is lower, yet the description still adds substantial substance: what a paused monitor stops doing (checking, recording heartbeats, alerting), what is preserved (configuration and history), and that resuming restarts checks immediately. The no-op statement on redundant writes corroborates the idempotentHint rather than contradicting it.

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 tight sentences with the core action front-loaded, followed by behavioral consequences and then alternatives. Every clause carries distinct information: state mapping, effects of pause, retention, resumption timing, and sibling routing.

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 toggle with a published output schema, the definition covers everything an agent needs: the action, the effect on monitoring behavior, data retention, restart semantics, no-op semantics, how to obtain the monitor ID, and which sibling handles scheduled downtime. Return values need not be explained given the output schema.

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 description coverage is 100% and both parameters are documented there, so the baseline is 3. The description restates the active boolean mapping already present in the schema; its only semantic addition is the no-op behavior when setting the current state, which is more about idempotency than parameter meaning.

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 pair and resource: pauses or resumes a monitor, with the boolean mapping given inline. It explicitly distinguishes itself from setMaintenanceWindowActive and createMaintenanceWindow, so an agent can separate monitor state from maintenance-window state without opening 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 Guidelines5/5

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

Explicit when-to-use (pause/resume a monitor) and when-not (planned downtime on a schedule should use createMaintenanceWindow instead), plus a clarification that setMaintenanceWindowActive acts on a maintenance window. It also routes the agent to listMonitors for ID discovery, leaving nothing to infer.

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