Skip to main content
Glama
Local Development MCP Server

Local Development MCP Server

by lreb

delete-task

Permanently removes a task from the local MCP task manager by ID, clearing unwanted entries from persistent storage.

Instructions

Permanently delete a task by ID

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": {
      "taskId": "<taskId>"
    },
    "name": "delete-task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesTask ID to delete (e.g. task-3)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the single most important trait: the deletion is permanent and irreversible. It stops there, saying nothing about whether confirmation is expected, what happens when the ID does not exist, or whether dependent records are affected.

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?

A single seven-word sentence with the destructive qualifier front-loaded where an agent will see it first. Nothing is wasted and nothing needs reordering.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is structurally simple (one required string, no output schema), so the description is close to sufficient. For an unannotated destructive operation, though, an agent would still benefit from knowing the failure behavior on an unknown ID and whether the call is idempotent.

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?

Only one parameter, and the schema already documents it at 100% coverage including an example value (task-3). The phrase "by ID" restates the schema rather than adding meaning, so the 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?

"Permanently delete a task by ID" gives a specific verb (delete), resource (task), effect qualifier (permanently) and lookup key (ID). It implicitly separates itself from update-task-status and list/search-tasks because removal is distinct from mutation or retrieval, though it never names a sibling to make the contrast explicit.

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?

Usage is only implied: the word "permanently" tells an agent this is the destructive path rather than a status change, but there is no stated when-to-use versus update-task-status, no precondition (must the task be complete first?), and no exclusion such as preferring an archive tool if one exists.

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