Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Complete Task

complete_task

Marks a specified runbook task as complete by providing the runbook ID and task ID.

Instructions

Complete 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": "complete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesThe ID of the task to complete.
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 supplied, so the description carries the full behavioral burden, yet it only implies a state transition via the verb 'complete'. It says nothing about permissions required, whether completion is reversible, what happens to dependent tasks, or idempotency on repeated calls — material for a mutation tool.

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 short sentence with no filler, and the core action is front-loaded. It is efficient but borders on under-specification rather than achieving the ideal of concise plus informative.

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, and the parameters are fully documented. But for a mutation tool with zero annotations, the definition omits preconditions, side effects, error conditions, and its relationship to sibling task-lifecycle tools, leaving the agent with too little to invoke it confidently.

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%: both runbook_id and task_id are documented in the input schema, so the description need not restate them. It adds no extra meaning such as ID format, lookup expectations, or how task_id is scoped to runbook_id, so 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?

States a specific verb and resource ('Complete a specific task in a runbook'), so an agent knows the operation targets a single task within a runbook. However, it offers no differentiation from siblings such as start_task, skip_task, or delete_task, which operate on the same resource and are easy to confuse with it.

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 description gives no when-to-use context, no prerequisites (e.g. whether the task must be started first), and never mentions alternatives. An agent must infer from the description alone whether to choose complete_task or skip_task/start_task.

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