Skip to main content
Glama
Sign In
mcp-taskflow

mcp-taskflow

by CalebGerman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_task

Remove a task by UUID: completed tasks are archived, while incomplete tasks are deleted.

Instructions

Delete a task. Completed tasks are archived, others are removed.

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
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3.1/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 full burden. It does disclose a genuinely useful behavioral trait — completed tasks are archived while others are permanently removed — which is exactly the kind of context a caller needs to avoid accidental data loss. However, it says nothing about whether the deletion is reversible, what permissions are required, or what happens to subtasks/dependents.

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?

Two short sentences, front-loaded with the action and immediately followed by the one behavioral fact that matters. No filler.

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?

For a destructive single-id operation with no annotations and no output schema, the description covers the core case but omits irreversibility, permission requirements, and error/not-found behavior. It is adequate but leaves real gaps for a delete tool.

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

Parameters2/5

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

The tool has one parameter (taskId, required, uuid) with 0% schema description coverage, so the description must compensate. It mentions no parameter at all — not which task identifier to pass, nor what happens if the id is unknown. Only the intuitive name 'taskId' makes this callable.

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+resource ('Delete a task') and adds the key behavioral distinction that completed tasks are archived whereas incomplete ones are removed. It is clear what the tool does, though it never names or contrasts with the obvious sibling clear_all_tasks, so an agent gets no help choosing between them.

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 when-to-use guidance and no exclusions. Given siblings like clear_all_tasks (bulk removal) and update_task, the description never says whether this is the single-task path or when clearing all tasks is preferable. Usage must be inferred entirely.

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