Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Schedule Maintenance

schedule_maintenance

Schedules a maintenance window for a hosted machine, previews who will be emailed, and confirms before applying it.

Instructions

Schedule a maintenance window on a hosted machine, like the console's Maintenance tab. machine is the machine_id from the machines tool, reason is required, and start and end are ISO 8601 times (UTC when they have no offset). The workspaces using the machine are emailed when it is scheduled. While the window is open their pods and volumes on it aren't billed and the machine earns nothing from them; pods keep running unless the work interrupts them. A regular window must start at least 48 hours ahead (insufficient_notice) and doesn't affect the uptime rate. emergency can start sooner but counts as downtime for the hours a client workload runs on the machine: set it only when the user chose emergency maintenance, never just to get past the notice. With confirm=false (default) it only checks the window and says who would be emailed, and schedules nothing; call again with confirm=true after the user agreed. The window starts by itself within about a minute of its start time; edit, extend, end or cancel it with maintenance_window. 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": {
      "machine": "<machine>",
      "reason": "<reason>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "schedule_maintenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
startYes
reasonYes
confirmNo
machineYes
emergencyNo
descriptionNo
operation_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only say this is a non-idempotent, non-destructive, open-world write; the description adds substantial context the annotations cannot carry: workspace emails on scheduling, billing and uptime consequences while the window is open, the pod-continuation caveat, the 48-hour rule with its error code (insufficient_notice), and the emergency-as-downtime tradeoff. It stops short of stating auth/permission requirements or what happens if a window overlaps an existing one.

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?

Dense but well front-loaded: identity and routing first, then behavioral consequences, then the preview/confirm protocol, then the operation_id contract. The closing operation_id paragraph is generic boilerplate and slightly dilutes an otherwise tight definition, but no sentence is wasted.

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 an 8-parameter mutation tool with an output schema, this covers what the schema and annotations cannot: side effects, timing rules, error conditions, retry/idempotency protocol, and lifecycle handoff to the maintenance_window tool. An agent has everything needed to call it safely and correctly.

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 0%, so the description must carry the load, and it does for most fields: machine is sourced from the machines tool, reason is marked required, start/end are ISO 8601 with UTC assumed when no offset is given, confirm defaults to false with preview semantics, and emergency and operation_id are both explained. The 'description' parameter is never mentioned, leaving one of eight fields undocumented.

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 concrete verb+resource ('Schedule a maintenance window on a hosted machine') and anchors it to a familiar analogue (the console's Maintenance tab). It also draws the boundary against the sibling that handles post-creation changes ('edit, extend, end or cancel it with maintenance_window'), so an agent can route correctly without opening either schema.

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?

Usage is fully specified: preview with confirm=false first and only re-call with confirm=true after the user agrees; use emergency only when the user explicitly chose it, never to bypass the 48-hour notice. The alternative tool for modifying an existing window is named explicitly.

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