Skip to main content
Glama

delete_task_comment

DestructiveIdempotent

Deletes a specific comment from a task using task ID and comment ID, removing outdated or incorrect discussion entries.

Instructions

Delete one of my task comments.

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>",
      "comment_id": "<comment_id>"
    },
    "name": "delete_task_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
comment_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is supplied by structured data rather than the description. The only added nuance is the word 'my', which hints at an ownership constraint but is ambiguous (the caller's comments only?) and says nothing about whether deletion is permanent, whether replies or notifications cascade, or what permission is required.

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?

One short, front-loaded sentence with zero filler, which is structurally fine. However, the brevity is under-specification rather than efficiency, so it only reaches the minimum-viable level.

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?

An output schema exists, so return values need not be described. But this is a destructive mutation with 0% parameter documentation, no annotation for scope or permissions, and no statement of permanence or cascading effects — several material gaps remain for a deletion 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?

Schema description coverage is 0% for both required parameters, so the description carries the burden of explaining task_id and comment_id — and it mentions neither. The type-level schema alone leaves an agent to guess whether task_id is even required alongside comment_id, or whether comment_id alone would suffice.

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 states a specific verb and resource ('Delete ... task comment'), so the operation is immediately identifiable and distinguishable by name from sibling mutations like edit_task_comment and delete_task. It stops short of explicitly contrasting itself with those siblings, which keeps it from a 5.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as edit_task_comment for softer correction or delete_task for the parent object. An agent must infer entirely from the name that this targets a single comment record.

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