Skip to main content
Glama

add_comment

Add comments or replies to tasks on FluentBoards project boards to facilitate team communication and task clarification.

Instructions

Add a comment to a task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYesBoard ID
task_idYesTask ID
commentYesComment text
comment_typeNoComment type - 'comment' for new comments, 'reply' for repliescomment
parent_idNoParent comment ID (required for replies)
notify_usersNoUser IDs to notify

Implementation Reference

  • Handler function that constructs the comment data from input arguments, conditionally adds parent_id and notify_users, makes a POST request to the API to add the comment to the specified task, and returns the formatted response.
    async (args) => {
      const {
        board_id,
        task_id,
        comment,
        comment_type,
        parent_id,
        notify_users,
      } = args;
    
      const commentData: any = {
        comment: comment,
        comment_type: comment_type,
      };
    
      if (parent_id) {
        commentData.parent_id = parent_id;
      }
    
      if (notify_users && notify_users.length > 0) {
        commentData.notify_users = notify_users;
      }
    
      const response = await api.post(
        `/projects/${board_id}/tasks/${task_id}/comments`,
        commentData
      );
      return formatResponse(response.data);
    }
  • Registers the 'add_comment' tool on the MCP server, including description, input schema using Zod, and the handler function.
    export function registerCommentTools(server: McpServer) {
      // Add a comment to a task
      server.tool(
        "add_comment",
        "Add a comment to a task",
        {
          board_id: z.number().int().positive().describe("Board ID"),
          task_id: z.number().int().positive().describe("Task ID"),
          comment: z.string().min(1).describe("Comment text"),
          comment_type: CommentTypeSchema.default("comment").describe(
            "Comment type - 'comment' for new comments, 'reply' for replies"
          ),
          parent_id: z
            .number()
            .int()
            .positive()
            .optional()
            .describe("Parent comment ID (required for replies)"),
          notify_users: z
            .array(z.number().int().positive())
            .optional()
            .describe("User IDs to notify"),
        },
        async (args) => {
          const {
            board_id,
            task_id,
            comment,
            comment_type,
            parent_id,
            notify_users,
          } = args;
    
          const commentData: any = {
            comment: comment,
            comment_type: comment_type,
          };
    
          if (parent_id) {
            commentData.parent_id = parent_id;
          }
    
          if (notify_users && notify_users.length > 0) {
            commentData.notify_users = notify_users;
          }
    
          const response = await api.post(
            `/projects/${board_id}/tasks/${task_id}/comments`,
            commentData
          );
          return formatResponse(response.data);
        }
      );
    }
  • Zod schema defining the input structure for adding a comment, matching the tool's parameters exactly.
    export const AddCommentSchema = z.object({
      board_id: z.number().int().positive(),
      task_id: z.number().int().positive(),
      comment: z.string().min(1),
      comment_type: CommentTypeSchema.default("comment"),
      parent_id: z.number().int().positive().optional(),
      notify_users: z.array(z.number().int().positive()).optional(),
    });
  • src/index.ts:24-24 (registration)
    Top-level registration call that invokes registerCommentTools to add the add_comment tool to the MCP server.
    registerCommentTools(server);
  • Helper schema for comment_type used within the add_comment tool's input schema.
    export const CommentTypeSchema = z.enum(["comment", "reply"]);
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 burden of behavioral disclosure. 'Add a comment' implies a write/mutation operation, but the description doesn't specify permissions required, whether the action is reversible, rate limits, or what happens on success/failure (e.g., returns a comment ID). For a mutation tool with zero annotation coverage, this leaves critical behavioral traits unaddressed.

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?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse. Every part of the sentence ('Add a comment to a task') directly contributes to understanding the tool's purpose without redundancy.

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?

Given the complexity (6 parameters, mutation operation) and lack of annotations or output schema, the description is incomplete. It doesn't cover behavioral aspects like side effects (e.g., notifications), error conditions, or return values. For a tool that modifies data, this leaves significant gaps for an AI agent to operate effectively.

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

Parameters3/5

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

Schema description coverage is 100%, with all parameters documented in the schema (e.g., 'comment_type' with enum values, 'parent_id' for replies). The description adds no parameter-specific information beyond the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 clearly states the action ('Add a comment') and the target resource ('to a task'), making the purpose immediately understandable. However, it doesn't distinguish this tool from potential sibling tools that might also involve comments, such as if there were 'edit_comment' or 'delete_comment' tools. The verb+resource combination is specific but lacks sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid board and task), exclusions (e.g., not for editing existing comments), or related tools (e.g., 'update_task' might handle task modifications). Without such context, the agent must infer usage from the tool name and parameters alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danieliser/fluent-boards-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server