Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Change a maintenance window

vs_maintenance_update
DestructiveIdempotent

Change a maintenance window's name, times, monitors or repeat. Send only the fields to change; monitorIds replaces the list.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "vs_maintenance_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMaintenance window id.
titleNoName of the maintenance, shown on status pages.
endTimeNoEnd, ISO 8601. At most 90 days after the start.
timezoneNoIANA time zone the repeat follows, for example Europe/London (default UTC).
startTimeNoStart, ISO 8601 (for example 2026-11-01T22:00:00Z).
monitorIdsNoMonitors covered. Their alerts are held back during the window.
descriptionNoOptional details.
recurrenceKindNoRepeat: none, day, week or month.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. The description adds one genuinely non-obvious behavior — that monitorIds replaces rather than merges — but says nothing about the consequences the destructive hint implies, e.g. that dropping ids ends their alert suppression.

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?

Two short sentences with no filler, and the field-changing guidance is front-loaded right after the purpose statement.

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 an 8-parameter mutation with no output schema, the description plus rich schema descriptions and annotations leave little ambiguity about how to call it. Minor gap: it does not note that partial updates leave unlisted fields untouched per-field while monitorIds behaves differently — the contrast is only half stated.

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 baseline is 3; the description earns above baseline by disclosing the replace-not-merge semantics of monitorIds, which the schema text ('Monitors covered...') does not convey. It omits mention of description and timezone, but those are fully documented in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Change a maintenance window') plus the editable dimensions (name, times, monitors, repeat), which cleanly separates it from vs_maintenance_create, vs_maintenance_cancel and vs_maintenance_delete. It does not name those siblings explicitly, so the differentiation is implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Send only the fields to change' gives real patch-level guidance on how to invoke it, but there is no statement of when to choose this over vs_maintenance_cancel (stop early) or vs_maintenance_delete (remove entirely), nor any prerequisite such as needing the window id first.

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

All Visual Sentinel 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