Skip to main content
Glama
Sign In
tick-mcp

tick-mcp

by KpihX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_task

Permanently delete a specific task from a project. Use this tool to remove a task irreversibly by providing project and task IDs.

Instructions

Permanently delete a task. ⚠️ IRREVERSIBLE.

[Category: Tasks — Write]  [Auth: V1]
[Related: complete_task, get_deleted_tasks]

Args:
    project_id: The project containing the task.
    task_id: The task to delete.

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

Input Schema

NameRequiredDescriptionDefault
project_idYes
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

The description highlights that deletion is permanent and irreversible, but no annotations are provided. It does not detail side effects like cascading deletes, error handling, or permission requirements, leaving some behavioral gaps.

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 very concise, using just 4 lines including the warning and metadata. It is front-loaded with the core action, and every sentence adds value.

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?

Given the simple parameters and no output schema, the description adequately covers purpose and inputs. It lacks details on return values or error scenarios, but the task is straightforward.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description adds meaningful context for both parameters: 'project_id' as 'The project containing the task' and 'task_id' as 'The task to delete.' This compensates for the lack of schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Permanently delete a task' with a strong warning of irreversibility. It distinguishes itself from sibling tools like 'complete_task' and 'get_deleted_tasks' via the 'Related' section.

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 description lacks explicit guidance on when to use this tool versus alternatives. While it lists related tools, it does not specify conditions for when delete is appropriate or when to avoid it.

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

Deploy Server

Other Tools