fettle-mcp

Overview Schema Source Related Servers Discussions Admin

Change settings of many monitors

bulk_update_monitors

Idempotent

Set the same interval, timeout, regions, channels, threshold, or cooldown on up to 100 monitors in one call, all or nothing.

Instructions

Set the same interval, timeout, regions, channels, threshold or cooldown on up to 100 monitors in one call, all or nothing. For example, move twenty PING monitors to other regions. Not for config or name (use update_monitor, one monitor at a time) or tags (use bulk_update_monitor_tags). Requires a key with the write scope. The plan's rules apply to the result: an interval below the plan minimum, too many fast monitors, too many regions or an unknown region is a 403. A value one monitor cannot take (several regions on an SSL, DNS or port-list TCP monitor, or an interval under 300 on a port-list one) is a 422 that starts with monitors[] (""). Returns monitors: list_monitors rows, which show the interval but not the other settings; read those with get_monitor. Example: {"monitor_ids": ["", ""], "changes": {"regions": ["eu-central", "us-east"], "interval_seconds": 300}}

Input Schema

TableJSON Schema

Name	Required	Description	Default
`changes`	Yes	The values to set, at least one of: interval_seconds (30 to 86400), timeout_seconds (1 to 120), regions (region codes from limits.allowed_regions in get_plan_usage), channel_ids (channel uuids from list_channels; replaces each binding, [] clears it, an unknown channel is a 404), confirmation_threshold (1 to 10) and notification_cooldown_seconds (60 to 86400). Omit a field to keep it; never send null.
`monitor_ids`	Yes	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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`monitors`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.6.1Oct 20, 2026

addedInput schema / properties / changes / description

Added value: +"The values to set, at least one of: interval_seconds (30 to 86400), timeout_seconds (1 to 120), regions (region codes from limits.allowed_regions in get_plan_usage), channel_ids (channel uuids from list_channels; replaces each binding, [] clears it, an unknown channel is a 404), confirmation_threshold (1 to 10) and notification_cooldown_seconds (60 to 86400). Omit a field to keep it; never send null."

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"
+}

First observedv0.5.4Oct 20, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover safety (readOnlyHint=false, idempotentHint=true, destructiveHint=false), and the description adds real behavior beyond them: atomic all-or-nothing semantics, 403 plan-rule failures, 422 per-monitor errors with the monitors[<i>] ("<name>") format, and the caveat that returned list_monitors rows omit most settings so get_monitor is needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and exclusions are front-loaded, and every sentence carries distinct information (scope, alternatives, auth, limits, error shapes, return caveat, example). It is dense and long, but no sentence is 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?

Given a 2-param tool with a nested changes object and an output schema, the description covers invocation, gating rules, partial-failure behavior, and result interpretation. An agent has everything needed to call it correctly.

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 nested changes object is fully documented in the schema, so baseline is 3. The description goes further with a concrete example payload and the semantics of channel_ids replacement/clearing and monitor_ids uniqueness/404 behavior, adding meaning beyond the raw 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?

Opens with a specific verb and resource ("Set the same interval, timeout, regions...") and bounds scope (up to 100 monitors, all-or-nothing). Explicitly names the siblings it is not (update_monitor, bulk_update_monitor_tags), so an agent can route correctly without opening schemas.

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?

States when-not to use it: not for config or name (use update_monitor) and not for tags (use bulk_update_monitor_tags). Also names the prerequisite (a key with write scope), which is the condition that gates invocation.

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

Deploy Server