Skip to main content
Glama

add_task_comment

Post a comment on a task to notify its people, with optional replies to existing comments and @mentions by name or ID.

Instructions

Post a comment on a task (the task's people are notified). reply_to = a comment id from get_task; mention = names/ids to @.

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>",
      "text": "<text>"
    },
    "name": "add_task_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
mentionNo
task_idYes
reply_toNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuinely new behavior beyond that: posting notifies the task's people, which is a side effect worth knowing before firing off a comment. It stops short of covering auth scope, rate limits, or whether editing/retracting is possible.

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

Conciseness4/5

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

Two compact lines with the primary action and its side effect front-loaded, followed by the two non-obvious parameter hints. The shorthand ('mention = names/ids to @') is slightly telegraphic but every clause carries information.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and annotations cover the safety profile. The description supplies the action, the notification side effect, and the tricky parameter semantics, leaving only minor gaps such as formatting support in comment text and permission requirements.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the load, and it explains the two parameters that are actually ambiguous: reply_to takes a comment id sourced from get_task, and mention accepts names or ids for @-mentioning. The remaining two (task_id, text) are self-evident from their names and required status.

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 and resource: 'Post a comment on a task', which cleanly separates it from siblings like get_task_comments, edit_task_comment, and delete_task_comment even though those names are not called out. The notification note adds scope (this is a visible, other-affecting write).

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 implied rather than stated: an agent can infer this is the tool for adding a new comment, and it points to get_task as the source of a reply_to id, which is a real workflow hint. However, there is no explicit when-to-use versus edit_task_comment/delete_task_comment guidance and no stated prerequisites.

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