Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Manage Runbook

manage_runbook

Start, pause, resume, or cancel a Cutover runbook by ID, with options for live or rehearsal runs, communications, notifications, and task timing adjustments.

Instructions

Manage a specific runbook by performing an action (start, cancel, pause, resume). These are the only possible actions with this tool.

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": {
      "runbook_id": "<runbook_id>",
      "action": "<action>"
    },
    "name": "manage_runbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
commsNoCommunication mode (off, test, on) (for start). Required by the platform; defaults to "off" so a start does not send communications unless asked to.off
actionYesThe action to perform (start, cancel, pause, resume).
notifyNoNotify users about the action (for cancel, pause, resume).
messageNoOptional message (for cancel, pause, resume).
run_typeNoType of run (live, rehearsal) (for start). Required by the platform; defaults to "rehearsal" — pass "live" explicitly to start a live run.rehearsal
rebaselineNoRecalculate all planned times based on the current time (for start).
runbook_idYesThe unique identifier for the runbook.
validation_levelNoValidation level (warning, error) (for start).error
shift_fixed_timesNoShift tasks with fixed times relative to the current time (for start).
disable_task_notifyNoDisable task start notifications (for start).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it discloses nothing about effects: whether cancel is reversible, what start does to task schedules, whether live runs send real notifications, or what permissions are needed. The most consequential detail (live vs rehearsal defaults) lives only in the schema, not the description.

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?

Two short, front-loaded sentences with the action set placed immediately after the purpose. The second sentence is mildly redundant with the enum but usefully forecloses the assumption of other actions.

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?

Given 10 parameters, full schema coverage, and an output schema, the description is not the weak link for parameter or return-value detail. What is missing is behavioral context for a mutation-heavy tool with no annotations: side effects, reversibility, and notification consequences are unaddressed.

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

Parameters3/5

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

Schema description coverage is 100% and the schema itself labels which parameters apply to start versus cancel/pause/resume, so the description need not compensate. It adds no parameter meaning of its own beyond repeating the action list.

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?

Names a specific resource (runbook) and a specific verb class (manage) with the four actions enumerated inline, so an agent knows exactly what operations are reachable. It stops short of differentiating from siblings such as update_runbook or create_runbook.

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

Usage Guidelines2/5

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

The only guidance is a constraint ('These are the only possible actions with this tool'), which is already implied by the action enum. There is no statement of when to pick this over update_runbook, create_runbook, or archive/delete workflows, nor any prerequisite context for starting a runbook.

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