fettle-mcp

Overview Schema Source Related Servers Discussions Admin

Resume a monitor

resume_monitor

Idempotent

Resume a paused monitor by returning its status to PENDING, so the scheduler checks it on the next tick. Use bulk resume for many monitors.

Instructions

Restart checks on one paused monitor: its status goes back to PENDING and it is checked on the scheduler's next tick. For many monitors use bulk_resume_monitors; to check a running monitor right away use check_now. Requires a key with the write scope. Resuming an active monitor is a no-op success. A 403 means the organization already has as many active monitors as its plan allows: pause or delete another one first. Returns the monitor in the get_monitor shape.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`monitor_id`	Yes	The monitor's uuid from list_monitors. An id that is not a monitor of this organization, or a deleted one, is a 404.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`name`	Yes
`tags`	No
`type`	Yes	Known values: HTTP, PING, SSL, TCP, DNS.
`config`	Yes
`status`	Yes	Known values: PENDING, UP, DEGRADED, DOWN, PAUSED.
`target`	Yes
`regions`	Yes
`user_id`	Yes
`is_active`	Yes
`created_at`	Yes
`updated_at`	Yes
`channel_ids`	No
`next_run_at`	Yes
`badge_enabled`	No
`ssl_cert_info`	No
`ssl_expires_at`	Yes
`last_checked_at`	Yes
`region_statuses`	Yes	Per-region latest status, sorted by region name. Built from ``region_snapshots``; ``job_id`` is dropped (internal dedup key) and malformed/partial snapshot rows are skipped rather than failing the read.
`timeout_seconds`	Yes
`interval_seconds`	Yes
`confirmation_threshold`	Yes
`notification_cooldown_seconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.6.1Oct 20, 2026

addedInput schema / properties / monitor_id / description

Added value: +"The monitor's uuid from list_monitors. An id that is not a monitor of this organization, or a deleted one, is a 404."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "badge_enabled": {
+      "type": "boolean"
+    },
+    "channel_ids": {
+      "items": {
+        "format": "uuid",
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "config": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "confirmation_threshold": {
+      "type": "integer"
+    },
+    "created_at": {
+      "type": "string"
+    },
+    "id": {
+      "format": "uuid",
+      "type": "string"
+    },
+    "interval_seconds": {
+      "type": "integer"
+    },
+    "is_active": {
+      "type": "boolean"
+    },
+    "last_checked_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "name": {
+      "type": "string"
+    },
+    "next_run_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "notification_cooldown_seconds": {
+      "type": "integer"
+    },
+    "region_statuses": {
+      "description": "Per-region latest status, sorted by region name.\n\nBuilt from ``region_snapshots``; ``job_id`` is dropped (internal\ndedup key) and malformed/partial snapshot rows are skipped rather\nthan failing the read.",
+      "items": {
+        "properties": {
+          "checked_at": {
+            "type": "string"
+          },
+          "display_name": {
+            "type": "string"
+          },
+          "region": {
+            "type": "string"
+          },
+          "status": {
+            "description": "Known values: UP, DEGRADED, DOWN, ERROR.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "region",
+          "status",
+          "checked_at",
+          "display_name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "regions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "ssl_cert_info": {
+      "anyOf": [
+        {
+          "properties": {
+            "issuer": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "not_after": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "not_before": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "subject": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "valid": {
+              "anyOf": [
+                {
+                  "type": "boolean"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "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"
+    },
+    "timeout_seconds": {
+      "type": "integer"
+    },
+    "type": {
+      "description": "Known values: HTTP, PING, SSL, TCP, DNS.",
+      "type": "string"
+    },
+    "updated_at": {
+      "type": "string"
+    },
+    "user_id": {
+      "format": "uuid",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "user_id",
+    "name",
+    "type",
+    "target",
+    "interval_seconds",
+    "timeout_seconds",
+    "regions",
+    "config",
+    "status",
+    "last_checked_at",
+    "next_run_at",
+    "confirmation_threshold",
+    "notification_cooldown_seconds",
+    "ssl_expires_at",
+    "is_active",
+    "created_at",
+    "updated_at",
+    "region_statuses"
+  ],
+  "type": "object"
+}

First observedv0.5.4Oct 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Goes well beyond the annotations: discloses the PENDING transition timing ('scheduler's next tick'), the required write scope, that active monitors yield a no-op success (consistent with idempotentHint), and the specific 403 plan-limit cause with a remediation. It does not add much on failure/retry edge cases, but the annotation set plus this text is unusually thorough.

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?

Four tight sentences with zero filler, front-loaded with the core action and its state change, then alternatives, then constraints. Every sentence carries distinct operational value.

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?

Covers the mental model (state transition), authorization requirement, idempotent-success case, a specific plan-limit failure with remedy, and the return shape by reference to get_monitor. Nothing an agent needs to call this 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 the single monitor_id param is fully documented there, including the 404 case. The description adds no new parameter-level syntax or format detail, so the baseline of 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 with explicit scope: 'Restart checks on one paused monitor.' The singular 'one' immediately distinguishes it from the bulk sibling, and the state transition (back to PENDING) makes the effect 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?

Explicitly routes to alternatives with conditions: 'For many monitors use bulk_resume_monitors; to check a running monitor right away use check_now.' That is textbook when-to-use/when-not guidance naming two concrete siblings.

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

Deploy Server