Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Skip Task

skip_task

Skip a specific task in a runbook by providing its task ID and a required reason comment. Use it to bypass tasks during cutover runs while recording why.

Instructions

Skip 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>",
      "comment": "<comment>"
    },
    "name": "skip_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentYesThe reason for skipping the task. Required by the API and added as a comment on the runbook.
task_idYesThe ID of the task to skip.
runbook_idYesThe ID of the runbook containing the task.

Output Schema

NameRequiredDescriptionDefault

No arguments

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 supplied, so the description carries the full burden, yet it says nothing about side effects: whether skipping is reversible, how the runbook's progress or downstream tasks are affected, or what permissions are needed. Only the schema's comment field hints at an API-level constraint (a reason is mandatory), which is structured-data context rather than description content.

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 zero filler. It is efficient, though for a mutation tool with no annotations the terseness borders on under-specification rather than ideal sizing.

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?

An output schema exists, so return values need not be described. However, this is an unannotated state-changing tool, and the description omits effects, reversibility, and preconditions — the exact areas structured fields do not cover.

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%, with each of the three parameters documented in-schema, including the requirement that comment is API-mandated. The description adds no meaning beyond that, so the baseline 3 applies.

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?

The description names a specific verb ('Skip') and a specific resource ('a task in a runbook'), so the action is unambiguous. It implicitly contrasts with sibling operations like complete_task or delete_task, but never states the distinction explicitly.

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 guidance on when to skip versus complete or delete a task, nor any prerequisites such as whether the task must be in a started state or whether the runbook must be active. The agent must infer all routing decisions from sibling names alone.

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