taskdog-mcp

cancel_task

Cancel a task using its ID, updating status to CANCELED and retrieving the revised task details.

Instructions

Cancel a task.

Changes status to CANCELED.

Args: task_id: ID of the task to cancel

Returns: Updated task data

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

Input Schema

Name	Required	Description	Default
`task_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.26.0Aug 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the status change and return value, but does not mention reversibility, permissions, or side effects on related tasks or dependencies. This leaves significant behavioral unknowns 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, front-loaded with the core action, and includes only necessary details. No redundant text or filler.

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?

For a simple one-parameter tool with an output schema, the description covers the basic action and return. However, it lacks contextual guidance on tool selection and potential side effects, so it is not fully complete for real-world decision-making.

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?

The description explains task_id as 'ID of the task to cancel', which adds a minimal gloss over the schema's bare integer field. With 0% schema description coverage, this is helpful but lacks additional context like required format or constraints.

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 clearly states the tool cancels a task and changes its status to CANCELED, which is specific and distinguishes it from delete_task or pause_task. However, it does not explicitly name alternative tools, so it stops short of the highest clarity rating.

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

Usage Guidelines3/5

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

The verb 'cancel' implies when to use the tool, and the status change to CANCELED hints at its intended use. Yet there is no explicit guidance on when to use cancel over pause, complete, or delete, especially with many relevant sibling tools.

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