OpenUptime

pause_monitor

Stop scheduled checks and alerts for one monitor while preserving its configuration and history; use it to temporarily halt monitoring, then resume when ready.

Instructions

Stop scheduled checks and alerts for one monitor, preserving its configuration and history; returns the paused monitor. Use this for a pause-only change, or update_monitor to combine a pause with configuration edits. For planned downtime that should still run checks, schedule maintenance through the app or REST API instead. Use resume_monitor to restart checking.

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": {
      "id": "<id>"
    },
    "name": "pause_monitor"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Resource UUID returned by the matching list tool; not its name, incident number or status-page slug.
`project`	No	Project id (from list_workspaces). Omit to use the default project of the workspace.
`workspace`	No	Workspace id (from list_workspaces). Omit to use the default one.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.1Oct 23, 2026

changedInput schema / properties / id / description

Previous value: -"Resource id (uuid)"New value: +"Resource UUID returned by the matching list tool; not its name, incident number or status-page slug."

First observedv0.1.0Oct 19, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the annotations, it discloses what is preserved (configuration and history) and that the paused monitor is returned, which matches destructiveHint=false. It doesn't say what happens when the monitor is already paused, which matters given idempotentHint=false, nor anything about permissions or alert-silencing nuances.

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 sentences, front-loaded with the core action and effect, followed by alternative routing and one exclusion. No sentence is redundant and nothing is buried.

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 mutation tool with no output schema, the description still states the effect (checks and alerts stop), the preserved state, and the return value, and it routes to the two sibling alternatives. Nothing an agent needs to call it correctly is missing.

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 each parameter (id, project, workspace) already documents its source and omission behavior. The description adds no parameter-level detail, so the baseline 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 ('Stop scheduled checks and alerts for one monitor') plus the key scope qualifier that configuration and history are preserved. It also explicitly separates itself from update_monitor and resume_monitor, so an agent can pick it without opening a 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?

The description gives a full decision tree: use this for a pause-only change, update_monitor to combine pause with edits, schedule maintenance for downtime that should still run checks, and resume_monitor to restart. Both positive selection criteria and exclusions are stated.

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