Skip to main content
Glama

Skip or move one occurrence

change_maintenance_occurrence
Idempotent

Skips (skipped: true), moves (starts_at and ends_at) or changes the message of one occurrence of a repeating maintenance window, leaving the others as they are; restore: true undoes it. Free.

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": {
      "window_id": "<window_id>",
      "occurrence_at": "<occurrence_at>"
    },
    "name": "change_maintenance_occurrence"
  }
}

Input Schema

NameRequiredDescriptionDefault
ends_atNoIts new end, after starts_at.
messageNoWhat visitors are told about this occurrence instead of the series' message.
restoreNotrue undoes every change to this occurrence.
skippedNotrue skips this occurrence: no maintenance then, and its status pages' subscribers hear it is cancelled if they were told about it.
starts_atNoMoves this occurrence: its new start, with ends_at.
window_idYesMaintenance window ID from list_maintenance_windows.
occurrence_atYesThe occurrence's start as the series gives it: occurrence_at from next_occurrences or occurrence_changes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only state that it is a non-destructive, idempotent mutation; the description adds the crucial scoping guarantee that other occurrences are untouched, plus the undo mechanism via restore:true and the plan note ('Free'). Those are behavioral facts an annotation could not express.

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

Conciseness3/5

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

One dense sentence with no wasted prose and the primary action front-loaded, but the parenthetical parameter citations make it read like syntax soup, and the trailing 'Free.' is cryptic without stating what it qualifies.

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?

With seven parameters, full schema coverage and no output schema, the definition covers the modes, the scoping rule, and the undo path. Only marginal gaps remain, such as whether skipped/moved/message changes can be combined in one call and what the call returns.

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 parameter docs already carry most meaning; the description still adds value by tying (skipped: true), (starts_at and ends_at) and message to the three distinct modes, showing that these parameters are the switches for different operations rather than independent knobs.

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 names a precise compound action on a precisely scoped resource: one occurrence of a repeating maintenance window, with the three supported modes (skip, move, change message) enumerated up front. 'Leaving the others as they are' implicitly but clearly separates it from series-level tools such as update_maintenance_window.

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

Usage Guidelines4/5

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

It makes clear the context in which to use it (editing a single occurrence rather than the whole series) and points to restore:true as the reversal path. It does not explicitly say when to prefer update_maintenance_window or delete_maintenance_window instead, so the exclusion is left to inference.

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