Skip to main content
Glama

Change a monitor's settings

update_monitor
DestructiveIdempotent

Use this when the user wants to change how a site or one of its checks is watched: a site's name, interval, timeout or group; a content check's text, selector, page, kind, attribute, limits, description, severity or interval; a dependency's name, description, severity or interval, and a plain HTTP dependency's URL and expected text; a cron job's schedule, grace period, longest run, description or severity. Returns the settings now in force. Only the fields given change. Not for pausing (use set_monitor_paused), deleting (the dashboard does that), or a dependency's components (plan it again with plan_dependency). Each setting is documented at https://flarewarden.com/docs/monitors.

Input Schema

NameRequiredDescriptionDefault
maxNoA content check's highest value allowed, for numeric_range or element_count.
minNoA content check's lowest value allowed, for numeric_range or element_count.
urlNoA plain HTTP dependency's URL; a status page dependency is changed with plan_dependency.
nameNoThe site's new name, or with check, the check's.
pageNoA content check's page path.
siteYesThe site, by id, name or part of its URL.
textNoA content check's text or pattern.
checkNoOne of the site's content checks, dependencies or cron jobs, by id or name; leave out to change the site itself.
graceNoA cron job's grace period in seconds.
groupNoA site's group; an empty string removes it.
matchNoHow expected_text is matched. Default contains.
max_runNoA cron job's longest normal run in seconds; 0 turns it off.
timeoutNoSeconds a site's checks wait for an answer before they count as failed (5, 10, 15 or 30; 10 unless changed). A longer one lets a slow page pass.
intervalNoSeconds between checks (30, 60, 300, 600, 1800 or 3600, as the plan allows).
scheduleNoA cron job's schedule: a cron expression (UTC), every N minutes, hours or days, or heartbeat.
selectorNoA content check's CSS selector.
severityNoHow serious a failure is.
attributeNoA content check's attribute to read, for attribute_check.
check_typeNoA content check's kind.
descriptionNoA check's description.
expected_textNoA plain HTTP dependency's text its answer must hold (or, with match, must not hold or match); an empty string stops checking it.
case_sensitiveNoWhether a content check matches case exactly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is known; the description adds genuinely non-derived semantics with 'Only the fields given change' (partial update, not replacement) and 'Returns the settings now in force' (post-mutation echo). It stops short of warning that overwriting a setting is not undoable, which would matter given destructiveHint=true.

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?

The trigger and the partial-update rule are front-loaded, and the closing sentence names the alternatives. The middle enumeration is one very long sentence and is denser than it needs to be, but each listed field set corresponds to a real target type and isn't filler.

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?

For a 22-parameter mutation with no output schema, the definition covers trigger, target selection, which fields apply where, partial-update behavior, the return value, and the escape hatches to siblings. The only missing piece an agent might want is failure/permission behavior, plus the pre-mutation create path (plan_* / add_*) for brand-new settings.

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%, so the per-parameter descriptions already carry most of the load and baseline 3 applies. The description still adds value by grouping the 22 flat parameters into target-type buckets (site vs. content check vs. dependency vs. cron job) and grouping them as 'limits', which helps the agent pick the right subset for the given target.

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 opens with a specific verb-plus-resource framing ('change how a site or one of its checks is watched') and then enumerates the exact field sets per target type (site, content check, dependency, cron job). It is easy to distinguish from add_*, plan_*, and set_monitor_paused siblings because it is explicitly a partial mutation of an existing monitor.

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?

It gives an explicit trigger ('when the user wants to change how a site or one of its checks is watched') plus three named exclusions with alternatives: pausing goes to set_monitor_paused, deleting happens in the dashboard, and dependency components go through plan_dependency. The `check` parameter's role ('leave out to change the site itself') further routes the agent between targets.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources