Skip to main content
Glama
fettlesh

fettle-mcp

by fettlesh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Pause many monitors

bulk_pause_monitors
Idempotent

Pause up to 100 monitors in one call, all or nothing: no checks run and open incidents close without alerts. Use for stopping a whole project or group found with list_monitors.

Instructions

Pause up to 100 monitors in one call, all or nothing: no checks run and each open incident closes without an alert. Use it to stop monitoring a whole project or group found with list_monitors; for one monitor use pause_monitor, and to silence alerts around a deploy while checks keep running use create_maintenance_window instead. Requires a key with the write scope. Pausing a paused monitor is not an error. Returns monitors: the list_monitors rows after the change, in request order. Example: {"monitor_ids": ["", ""]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monitor_idsYes1 to 100 distinct monitor uuids from list_monitors. A repeated id is a 422; an id that is not a monitor of this organization is a 404 naming it, and then nothing changes.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
monitorsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.1
    • changedInput schema / properties / monitor_ids / description
      Previous value: -"Monitors to act on. Every id must belong to the active organization."New value: +"1 to 100 distinct monitor uuids from list_monitors. A repeated id is a 422; an id that is not a monitor of this organization is a 404 naming it, and then nothing changes."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "monitors": {
+      "items": {
+        "properties": {
+          "id": {
+            "format": "uuid",
+            "type": "string"
+          },
+          "interval_seconds": {
+            "type": "integer"
+          },
+          "is_active": {
+            "type": "boolean"
+          },
+          "last_checked_at": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "ssl_expires_at": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "status": {
+            "description": "Known values: PENDING, UP, DEGRADED, DOWN, PAUSED.",
+            "type": "string"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "target": {
+            "type": "string"
+          },
+          "type": {
+            "description": "Known values: HTTP, PING, SSL, TCP, DNS.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "type",
+          "target",
+          "status",
+          "is_active",
+          "interval_seconds",
+          "ssl_expires_at",
+          "last_checked_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "monitors"
+  ],
+  "type": "object"
+}
  2. First observedv0.5.4

TDQS

A4.9/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: all-or-nothing atomicity, that no checks run and open incidents close without alert, the write-scope requirement, and that re-pausing is not an error. These are behavioral facts the idempotent/destructive hints alone would not convey.

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?

Front-loads the action and scope, then routes to alternatives, then states prerequisites and return shape. Dense but every sentence carries distinct information; no filler.

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?

An output schema exists, yet the description still names the return ('list_monitors rows after the change, in request order'), and the auth requirement plus atomicity behavior are covered. Nothing needed to invoke it correctly is missing.

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 documents the 422 duplicate-id and 404 unknown-id behavior, so the baseline is 3. The description's inline example clarifies invocation format and reinforces the atomic failure semantics ('all or nothing'), adding modest value over the schema.

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 with scope: 'Pause up to 100 monitors in one call'. It also explicitly distinguishes itself from pause_monitor (single) and create_maintenance_window (silence while checks run), so the sibling boundary is unambiguous.

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 when-to-use ('stop monitoring a whole project or group found with list_monitors') plus two named alternatives with the condition that selects each. No inference required.

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

Deploy Server

Other Tools