Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Start Task

start_task

Initiate a specific task within a Cutover runbook by providing the runbook ID and task ID to begin execution.

Instructions

Start a specific task in a runbook.

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>",
      "task_id": "<task_id>"
    },
    "name": "start_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesThe ID of the task to start.
runbook_idYesThe ID of the runbook containing the task.

Output Schema

NameRequiredDescriptionDefault
dataYes
includedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 full behavioral burden. It does not disclose whether the operation is idempotent, what state changes it triggers (e.g., status transitions, timestamps, activity log entries), whether it fails if the task is already started, or what permissions are required.

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?

A single front-loaded sentence with no redundant wording. It is efficient, though the terseness borders on under-specification given the mutation semantics.

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

Completeness2/5

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

The output schema covers return values and the schema covers both parameters, but for a state-changing operation with zero annotations, the description omits side effects, failure conditions, and permission requirements. An agent has no way to know from this definition what starting a task actually does.

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 coverage is 100%, with both runbook_id and task_id documented inline, so the description appropriately adds nothing further. It could have clarified the relationship between runbook_id and task_id (that task_id must belong to runbook_id), which the schema leaves implicit.

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 ('Start a specific task in a runbook'), so an agent knows exactly what action is performed. It does not differentiate against siblings such as complete_task or skip_task, leaving the reader to infer the distinction from names alone.

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?

There is no when-to-use guidance at all. The definition never says when starting a task is appropriate versus completing, skipping, or updating it, and gives no prerequisites such as whether the task must already be assigned or unblocked.

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