Skip to main content
Glama
Sign In
Cortex Intelligent

Cortex Intelligent

by adyoi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

task_delete

Delete a task by its ID from persistent task management, removing completed, canceled, or obsolete items so plans and project tracking stay accurate.

Instructions

Delete a 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": {
      "id": "<id>"
    },
    "name": "task_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden and largely fails it. It implies a destructive mutation but says nothing about reversibility, whether subtasks or linked records are cascaded, or what permissions are required. Only the barest signal (this is a delete) is conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The single sentence is front-loaded and free of waste, which is appropriate in size. But brevity here shades into under-specification rather than discipline, since nothing beyond the verb+resource is offered for a destructive operation.

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

Completeness2/5

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

For a destructive tool with no annotations, no output schema, and an undocumented parameter, the description is too thin. An agent cannot determine consequences of the call (permanent removal, cascade behaviour, error conditions), which is the minimum needed before invoking a delete.

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 input schema has 0% description coverage for the single required 'id' parameter, and the description does not compensate by explaining the identifier's expected form or source. The agent must infer that 'id' is a task identifier, which is plausible but unstated.

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 names a specific verb and resource ('Delete a task'), so the core operation is unambiguous. However, it offers no differentiation from the many sibling task tools (task_done, task_block, task_create), so an agent cannot tell from the text whether deletion is the same as marking done or a distinct destructive action.

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, no mention of prerequisites, and no routing to alternatives such as task_done/task_block for soft state changes. The agent gets only the operation name, not the conditions under which it should be preferred over the rest of the task lifecycle family.

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