Skip to main content
Glama

Relvato

by com.relvato.app
OverviewDiscussionsAdmin

Update a monitor

update_check
Idempotent

Turn a monitor on or off, or change when it runs: its schedule (up to weekly on Free, daily on Pro, hourly on Business, every 15 minutes on Agency), re-runs when the WordPress site changes (plugin, theme, core or WooCommerce updates; Pro and up) and random extra runs (Business and up). Only the fields you pass change. Its own settings (pages, URLs, checkout details) are changed with update_check_settings or update_visual_monitor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
atNoDaily/weekly run time, HH:MM (24h)
tzNoIANA timezone for `at`, e.g. Europe/Berlin
dowNoWeekly only: weekday, 0 = Sunday … 6 = Saturday
eventsNoWordPress sites only: re-run when these change. [] = none. A monitor's built-in triggers (e.g. the admin roster's role changes) are kept.
randomNoRandom extra runs (times per days), with an off or weekly schedule; null turns them off
checkIdYesThe monitor's id (from site_overview or add_checks)
enabledNoTurn the monitor on or off
scheduleNoRecurring schedule

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / events
      Added value: +{
+  "description": "WordPress sites only: re-run when these change. [] = none. A monitor's built-in triggers (e.g. the admin roster's role changes) are kept.",
+  "items": {
+    "enum": [
+      "plugin",
+      "theme",
+      "core",
+      "woocommerce"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / random
      Added value: +{
+  "additionalProperties": false,
+  "description": "Random extra runs (times per days), with an off or weekly schedule; null turns them off",
+  "properties": {
+    "days": {
+      "description": "over 1-365 days",
+      "type": "number"
+    },
+    "times": {
+      "description": "1-100 runs",
+      "type": "number"
+    }
+  },
+  "required": [
+    "times",
+    "days"
+  ],
+  "type": [
+    "object",
+    "null"
+  ]
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / checkId / description
      Previous value: -"The check id (from site_overview or add_checks)"New value: +"The monitor's id (from site_overview or add_checks)"
    • changedInput schema / properties / enabled / description
      Previous value: -"Turn the check on or off"New value: +"Turn the monitor on or off"
  3. 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 the operation as non-readonly, idempotent, non-destructive, and closed-world. The description adds important context beyond annotations: partial-update behavior, plan-tier availability for schedule/events/random runs, and which specialized sibling handles settings fields.

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?

Front-loads the core action and then lists the attribute groups that can be changed. It is dense but efficient, with no redundant filler or repeated schema text.

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?

The description is complete enough for a mutation tool with full schema descriptions and no output schema. It covers scope, plan limits, and sibling alternatives, though it does not discuss error behavior or response shape.

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 schema already documents each parameter. The description still adds meaning by tying schedule, events, and random parameters to plan tiers and by clarifying that unspecified fields are left unchanged.

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: updating a monitor's enabled state, schedule, event triggers, or random runs. It also explicitly distinguishes these fields from the monitor's own settings, which are handled by update_check_settings or update_visual_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?

Tells the agent exactly what this tool changes and what it does not: only passed fields change, and pages, URLs, and checkout details require update_check_settings or update_visual_monitor. Plan-tier constraints are also given for schedule, events, and random runs.

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

All Relvato toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources