UptyBots

Pause monitor

pause_monitor

Idempotent

Stop checking a monitor without deleting it. History and configuration survive, and resume_monitor puts it back to work. Use this around planned maintenance so the downtime does not land in the uptime figures or fire alerts. A paused monitor reports neither up nor down, so it is easy to forget one is off.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Monitor id to pause, as returned by list_monitors.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Monitor id, used by every other tool.
`url`	No
`name`	No
`type`	No
`isActive`	No	False while the monitor is paused.
`frequency`	No	Check interval in minutes.
`statusSummary`	No	Current state, for example GOOD or ERROR.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 20, 2026

changedInput schema / properties / id / description

Previous value: -"Monitor ID to pause"New value: +"Monitor id to pause, as returned by list_monitors."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "frequency": {
+      "description": "Check interval in minutes.",
+      "type": "integer"
+    },
+    "id": {
+      "description": "Monitor id, used by every other tool.",
+      "type": "integer"
+    },
+    "isActive": {
+      "description": "False while the monitor is paused.",
+      "type": "boolean"
+    },
+    "name": {
+      "type": "string"
+    },
+    "statusSummary": {
+      "description": "Current state, for example GOOD or ERROR.",
+      "type": "string"
+    },
+    "type": {
+      "enum": [
+        "PING",
+        "HTTP",
+        "API",
+        "SSL",
+        "DOMAIN",
+        "PORT"
+      ],
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id"
+  ],
+  "type": "object"
+}

First observedAug 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=false, destructive=false, and idempotent=true. The description adds that the monitor is not deleted, history/config survive, and it reports neither up nor down while paused. This enriches beyond the annotations.

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?

The description is concise, three sentences, each adding value: what it does, when to use it, and behavioral nuance. No fluff.

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?

Given the tool's simplicity (one parameter), the description adequately covers purpose, usage, and behavior. The output schema exists, so return values are presumably covered there. It's complete enough.

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?

The schema fully describes the 'id' parameter (100% coverage) with a clear description. The tool description doesn't add much beyond that, but since schema coverage is high, baseline 3 is appropriate.

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?

The description clearly states it stops checking a monitor without deleting it, while preserving history and configuration. It distinguishes itself from delete_monitor and resume_monitor by explicitly mentioning these sibling tools.

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?

It provides context for use around planned maintenance to avoid downtime affecting uptime figures or triggering alerts. It doesn't explicitly exclude other tools or state when not to use, but the context implies use cases. Sibling tools are listed, giving alternatives.

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

All UptyBots tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?