delete_task
Permanently delete a task by specifying its task ID.
Instructions
Delete a task
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| taskId | Yes | Task ID |
Permanently delete a task by specifying its task ID.
Delete a task
| Name | Required | Description | Default |
|---|---|---|---|
| taskId | Yes | Task ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, and the description only says 'Delete a task' without disclosing behavioral traits such as whether deletion is permanent, cascading effects, or return value. This is insufficient for a destructive operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no wasted words, but could be slightly more informative without losing conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple delete-by-ID tool with no output schema, the description is minimally adequate but lacks details on return behavior or error conditions.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% (taskId described), so baseline is 3. The description adds no additional meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Delete a task' clearly states the action and resource, distinguishing it from sibling tools like create_task, get_task, list_tasks, and update_task.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use (when you want to delete a task) but provides no explicit guidance on prerequisites, side effects, or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Aayush9029/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server