Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Delete Task

delete_task

Delete one task from a Cutover runbook by providing the runbook ID and task ID, keeping runbook task lists accurate and current.

Instructions

Delete a single task from 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": "delete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesThe ID of the task to delete.
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 behavioral burden, yet it says nothing about irreversibility, whether attached comments/attachments/completion history are removed, or what permissions are required. The verb 'Delete' implies mutation, but that is the only behavioral signal the agent gets for a destructive operation.

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; the action and target resource come first. It is efficient, though the brevity is partly under-specification rather than disciplined concision.

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 explained, but for a destructive tool with no annotations the description should at least flag irreversibility and side effects. As written, an agent knows what to call but not what it risks destroying.

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 both parameters are documented in the schema themselves, so baseline 3 applies. The description's phrase 'from a runbook' loosely reinforces the runbook_id/task_id relationship but adds no format, constraint, or validation detail beyond the schema.

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 pair ('Delete a single task') and scopes it to 'from a runbook', which is enough for an agent to distinguish it from list/update siblings such as update_runbook_task or get_runbook_tasks. It stops short of explicitly naming an alternative or clarifying how it differs from skip_task/complete_task, so it is clear but not sibling-differentiating.

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, no mention of preconditions, and no pointer to alternatives like skip_task or archive flows. The agent must infer that this is the destructive removal path from the verb alone.

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