Skip to main content
Glama

Retune monitor

update_monitor
DestructiveIdempotent

Change how loudly a monitor is watched: check interval, alert confirmations, recovery notices, reminder interval, tags, group, the multi-region detection quorum, and which notification channels it alerts (channel_ids replaces the whole set, and needs the channels:read scope). It cannot change what the check watches — name, address, assertions, expected status, headers, body, probe regions and owner are refused. A monitor managed by Terraform is refused outright. Shows the old and new value of every field before it runs, where the client can show a prompt; otherwise runs on the token's scope. Not read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe monitor id (from `list_monitors`).
tagsNoReplaces the whole tag list. Read the monitor first: a tag left out of this list is removed. At most 50 tags, each at most 50 characters.
group_nameNoOperator-side grouping label. Send `null` to clear it; omit to keep it.
channel_idsNoReplaces the whole set of alerted channels, by id from `list_notification_channels`. Read the monitor first: a channel left out of this list stops being alerted. An empty list silences the monitor.
interval_secsNoSeconds between checks. Held to the plan's floor and the check kind's own floor, whichever is higher.
region_policyNoDetection quorum across probe regions.
notify_recoveryNoWhether recovery is announced to the monitor's channels.
alert_confirmationsNoConsecutive failing checks before the monitor alerts. Minimum 1. Raising it quietens a flapping monitor at the cost of alerting later.
recovery_period_secsNoSeconds a recovered monitor must stay healthy before its incident closes, 0 to 1800. Raising it folds a flapping monitor's short outages into one incident, at the cost of announcing recovery later.
renotify_interval_secsNoSeconds before the first reminder while an outage stays unacknowledged; each further reminder waits twice as long, up to a day. 0 turns reminders off; otherwise at least 60.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
changesYesWhat moved. Empty when every value sent already matched the stored one, in which case nothing was written and no confirmation was asked for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / recovery_period_secs
      Added value: +{
      +  "description": "Seconds a recovered monitor must stay healthy before its incident\ncloses, 0 to 1800. Raising it folds a flapping monitor's short outages\ninto one incident, at the cost of announcing recovery later.",
      +  "format": "uint32",
      +  "minimum": 0,
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
  2. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.