Skip to main content
Glama
Sign In
Local Task Manager MCP Server

Local Task Manager MCP Server

by akbarshaik2243
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

delete_task

Delete a task by providing its ID; the deleted task is returned for confirmation.

Instructions

Delete a task by ID and return the deleted task.

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": "delete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
titleYes
completedYes
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must fully disclose behavior. It states that the tool returns the deleted task, which adds some transparency, but it does not mention side effects (e.g., irreversibility), authorization needs, or the permanence of deletion.

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 a single sentence that efficiently conveys the core action and return value, with no extraneous information.

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 delete operation with one parameter and no annotations, the description covers purpose and return value. However, it lacks comparison to sibling tools (e.g., when to delete vs. complete) and does not mention any confirmation or undo behavior.

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 mentions 'by ID', which contextualizes the task_id parameter beyond the schema title, but does not explain how to obtain the ID or its format. With 0% schema description coverage, the description provides minimal added meaning.

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 the verb 'delete' and the resource 'task', and specifies that it returns the deleted task. This distinguishes it from siblings like list_tasks (does not delete) and complete_task (does not delete).

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?

No guidance is provided on when to use this tool versus alternatives such as complete_task. The description does not mention prerequisites or conditions for deletion.

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