Skip to main content
Glama
its-dart

Dart MCP Server

by its-dart

add_task_comment

Add markdown-formatted comments to specific tasks in Dart project management without altering task descriptions, enhancing task clarity and collaboration.

Instructions

Add a comment to an existing task without modifying the task description. Comments support markdown formatting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesThe 12-character alphanumeric ID of the task
textYesThe full content of the comment, which can include markdown formatting.

Implementation Reference

  • The switch case in the CallToolRequestSchema handler that implements the logic for the 'add_task_comment' tool: validates taskId, constructs comment data, calls CommentService.addTaskComment, and returns the JSON stringified result.
    case ADD_TASK_COMMENT_TOOL.name: {
      const taskId = getIdValidated(args.taskId);
      const text = args.text;
      const commentData = { taskId, text } as CommentCreate;
      const comment = await CommentService.addTaskComment({
        item: commentData,
      });
      return {
        content: [{ type: "text", text: JSON.stringify(comment, null, 2) }],
      };
    }
  • The Tool object definition for 'add_task_comment', specifying the name, description, and inputSchema with required taskId and text parameters.
    export const ADD_TASK_COMMENT_TOOL: Tool = {
      name: "add_task_comment",
      description:
        "Add a comment to an existing task without modifying the task description. Comments support markdown formatting.",
      inputSchema: {
        type: "object",
        properties: {
          taskId: {
            type: "string",
            description: "The 12-character alphanumeric ID of the task",
            pattern: "^[a-zA-Z0-9]{12}$",
          },
          text: {
            type: "string",
            description:
              "The full content of the comment, which can include markdown formatting.",
          },
        },
        required: ["taskId", "text"],
      },
    };
  • index.ts:192-214 (registration)
    The TOOLS array registers ADD_TASK_COMMENT_TOOL among other tools, which is provided in response to ListToolsRequestSchema.
    const TOOLS = [
      // Config
      GET_CONFIG_TOOL,
      // Tasks
      CREATE_TASK_TOOL,
      LIST_TASKS_TOOL,
      GET_TASK_TOOL,
      UPDATE_TASK_TOOL,
      DELETE_TASK_TOOL,
      // Docs
      CREATE_DOC_TOOL,
      LIST_DOCS_TOOL,
      GET_DOC_TOOL,
      UPDATE_DOC_TOOL,
      DELETE_DOC_TOOL,
      // Comments
      ADD_TASK_COMMENT_TOOL,
      LIST_TASK_COMMENTS_TOOL,
      // Other
      GET_DARTBOARD_TOOL,
      GET_FOLDER_TOOL,
      GET_VIEW_TOOL,
    ];
  • index.ts:35-52 (registration)
    Import statement that brings ADD_TASK_COMMENT_TOOL into index.ts for use in handlers and registration.
    import {
      ADD_TASK_COMMENT_TOOL,
      CREATE_DOC_TOOL,
      CREATE_TASK_TOOL,
      DELETE_DOC_TOOL,
      DELETE_TASK_TOOL,
      GET_CONFIG_TOOL,
      GET_DARTBOARD_TOOL,
      GET_DOC_TOOL,
      GET_FOLDER_TOOL,
      GET_TASK_TOOL,
      GET_VIEW_TOOL,
      LIST_DOCS_TOOL,
      LIST_TASK_COMMENTS_TOOL,
      LIST_TASKS_TOOL,
      UPDATE_DOC_TOOL,
      UPDATE_TASK_TOOL,
    } from "./tools.js";
Behavior3/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. It discloses that comments support markdown formatting, which is useful behavioral context. However, it lacks details on permissions, rate limits, or response format, leaving gaps for a mutation tool.

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 front-loaded and concise, consisting of two sentences that efficiently convey the tool's purpose and key feature (markdown support) without any wasted words. Every sentence earns its place.

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

Completeness3/5

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

Given the tool's moderate complexity (a mutation with two parameters) and no annotations or output schema, the description is adequate but incomplete. It covers the basic purpose and markdown support, but lacks details on behavioral aspects like error handling or return values, which are important for an agent.

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%, so the schema already documents both parameters (taskId and text) thoroughly. The description adds minimal value by mentioning markdown formatting for the text parameter, but does not provide additional semantics beyond what the schema offers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Add a comment') and resource ('to an existing task'), distinguishing it from sibling tools like create_task, update_task, and list_task_comments. It explicitly notes that it does not modify the task description, which further clarifies its purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context by specifying that comments are added to existing tasks, implying when to use it (after task creation). However, it does not explicitly state when not to use it or name alternatives, such as using update_task for modifying the task description instead.

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

Related 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/its-dart/dart-mcp-server'

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