Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Change Maintenance Window

maintenance_window
Idempotent

Edit, cancel, extend, or end a hosted machine's maintenance window; preview changes first with confirm=false, then confirm to apply them.

Instructions

Change one maintenance window of a hosted machine, like the buttons in the console's Maintenance tab. maintenance_id is a window id from the machines tool (a machine's maintenance). action "edit" changes a window that hasn't started: pass only what changes among reason, description, start and end (ISO 8601, UTC when there is no offset). New times email the affected workspaces again, and a regular window still needs 48 hours' notice unless it only moves later. "cancel" removes a window that hasn't started, for good; the workspaces that were notified get no cancellation email. "extend" makes a window in progress longer by hours (more than 0) and needs a reason, which the affected workspaces are emailed. "end" closes a window in progress now: pods and volumes on the machine are billed again from then on, and the machine comes back online but unlisted until it is listed again (set_machine_listing). There is no action to start a window: it starts by itself within about a minute of its start time. With confirm=false (default) it only shows the window and what the action does, and changes nothing; call again with confirm=true after the user agreed. Every write requires operation_id. Reuse the ID returned by the preview, or generate a UUID before the first call. Keep it for confirmation and all retries; a new ID means a new operation. After a timeout, check operation_status and resource state before retrying.

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": {
      "maintenance_id": "<maintenance_id>"
    },
    "name": "maintenance_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
hoursNo
startNo
actionNoedit
reasonNo
confirmNo
descriptionNo
operation_idNo
maintenance_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.7/5.0
Behavior4/5

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

Discloses consequences well beyond the annotations: cancellation is permanent and sends no email, extend emails affected workspaces and requires a reason, and 'end' resumes billing and leaves the machine online but unlisted until set_machine_listing is called. The one soft spot is that "cancel removes a window ... for good" sits slightly at odds with destructiveHint=false, though the annotations otherwise match the described behavior.

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?

Purpose is front-loaded, then actions are introduced in quoted, scannable order, followed by the confirm and operation_id protocols. It is dense and every sentence carries information, though a few sentences run long by chaining multiple rules together.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter mutation tool with a preview/confirm flow, the definition covers preconditions, side effects, retry-after-timeout guidance, and cross-tool follow-up (set_machine_listing, operation_status). Return values need not be described because an output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description carries the full load and does: it defines maintenance_id's origin (a machine's `maintenance` id), enumerates action values, scopes reason/description/start/end to the edit path, constrains hours to >0 for extend, specifies ISO 8601 with UTC-when-no-offset, and explains confirm's default false semantics. operation_id's lifecycle is also fully described.

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 ("Change one maintenance window of a hosted machine") and anchors it to a familiar console affordance, so an agent knows exactly which object is mutated. The four named actions (edit/cancel/extend/end) plus the explicit note that there is no 'start' action sharply delimit the scope against a scheduling sibling like schedule_maintenance.

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?

Gives per-action preconditions (edit/cancel only on windows that haven't started, extend/end only on windows in progress), an explicit exclusion ("There is no action to start a window"), and the 48-hour notice rule. The two-step confirm protocol and the operation_id reuse/retry rule make the call sequence unambiguous.

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