Skip to main content
Glama
its-dart

Dart MCP Server

by its-dart

create_task

Create and manage tasks in Dart by specifying title, description, status, priority, assignees, tags, dates, parent task, and custom properties. Ideal for AI-driven project management and task organization.

Instructions

Create a new task in Dart. You can specify title, description, status, priority, size, dates, dartboard, assignees, tags, parent task, custom properties, and task relationships.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assigneeNoSingle assignee name or email (if workspace doesn't allow multiple assignees)
assigneesNoArray of assignee names or emails (if workspace allows multiple assignees)
customPropertiesNoCustom properties to apply to the task. Use the property names from the config. Examples: { 'customCheckboxProperty': true, 'customTextProperty': 'Some text', 'customNumberProperty': 5, 'customSelectProperty': 'Option Name', 'customDatesProperty': '2025-05-10', 'customDatesPropertyWithRange': ['2025-05-01', '2025-05-30'], 'customMultiselectProperty': ['option1', 'option2'], 'customUserProperty': 'user@example.com', 'customMultipleUserProperty': ['user1@example.com', 'user2@example.com'], 'customTimeTrackingProperty': '1:30:00' }
dartboardNoThe title of the dartboard (project or list of tasks)
descriptionNoA longer description of the task, which can include markdown formatting
dueAtNoThe due date in ISO format (should be at 9:00am in user's timezone)
parentIdNoThe ID of the parent task
priorityNoThe priority (Critical, High, Medium, or Low)
sizeNoThe size which represents the amount of work needed
startAtNoThe start date in ISO format (should be at 9:00am in user's timezone)
statusNoThe status from the list of available statuses
tagsNoArray of tags to apply to the task
taskRelationshipsNoTask relationships including subtasks, blockers, duplicates, and related tasks
titleYesThe title of the task (required)
typeNoThe type of the task from the list of available types

Implementation Reference

  • Handler implementation for the 'create_task' tool within the CallToolRequestSchema switch statement. It casts the input arguments to TaskCreate type and delegates the task creation to TaskService.createTask, then returns the result as JSON text.
    case CREATE_TASK_TOOL.name: {
      const taskData = args as TaskCreate;
      const task = await TaskService.createTask({ item: taskData });
      return {
        content: [{ type: "text", text: JSON.stringify(task, null, 2) }],
      };
    }
  • Tool schema definition for 'create_task', including name, detailed description, and comprehensive inputSchema with properties for task attributes, custom properties, and relationships.
    export const CREATE_TASK_TOOL: Tool = {
      name: "create_task",
      description:
        "Create a new task in Dart. You can specify title, description, status, priority, size, dates, dartboard, assignees, tags, parent task, custom properties, and task relationships.",
      inputSchema: {
        type: "object",
        properties: {
          title: {
            type: "string",
            description: "The title of the task (required)",
          },
          description: {
            type: "string",
            description:
              "A longer description of the task, which can include markdown formatting",
          },
          dartboard: {
            type: "string",
            description: "The title of the dartboard (project or list of tasks)",
          },
          parentId: {
            type: "string",
            description: "The ID of the parent task",
            pattern: "^[a-zA-Z0-9]{12}$",
          },
          status: {
            type: "string",
            description: "The status from the list of available statuses",
          },
          type: {
            type: "string",
            description: "The type of the task from the list of available types",
          },
          assignees: {
            type: "array",
            items: { type: "string" },
            description:
              "Array of assignee names or emails (if workspace allows multiple assignees)",
          },
          assignee: {
            type: "string",
            description:
              "Single assignee name or email (if workspace doesn't allow multiple assignees)",
          },
          priority: {
            type: "string",
            description: "The priority (Critical, High, Medium, or Low)",
          },
          tags: {
            type: "array",
            items: { type: "string" },
            description: "Array of tags to apply to the task",
          },
          size: {
            type: ["string", "number", "null"],
            description: "The size which represents the amount of work needed",
          },
          startAt: {
            type: "string",
            description:
              "The start date in ISO format (should be at 9:00am in user's timezone)",
          },
          dueAt: {
            type: "string",
            description:
              "The due date in ISO format (should be at 9:00am in user's timezone)",
          },
          customProperties: CUSTOM_PROPERTIES_SCHEMA,
          taskRelationships: TASK_RELATIONSHIPS_SCHEMA,
        },
        required: ["title"],
      },
    };
  • index.ts:192-214 (registration)
    Registration of the 'create_task' tool (as CREATE_TASK_TOOL) in the TOOLS array, which is returned by ListToolsRequestSchema handler to expose available tools.
    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:36-52 (registration)
    Import of CREATE_TASK_TOOL from tools.ts (noted as tools.js in code), making it available for registration and use in handlers.
      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";
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a task but doesn't mention potential side effects (e.g., notifications sent, audit logs), error conditions, or response format. This is inadequate for a mutation tool with complex parameters.

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?

The description is a single, efficient sentence that front-loads the core action and enumerates key parameters. It avoids redundancy but could be slightly more structured by grouping related fields or highlighting required ones.

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?

For a complex mutation tool with 15 parameters, no annotations, and no output schema, the description is insufficient. It doesn't address behavioral aspects, error handling, or return values, leaving significant gaps for an AI agent to invoke it correctly.

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?

The description lists parameter fields (e.g., title, description, status) but doesn't add meaningful semantics beyond what the schema already provides (100% coverage). It serves as a high-level overview without clarifying interdependencies or usage nuances, meeting the baseline for high schema coverage.

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 verb ('Create') and resource ('new task in Dart'), making the purpose evident. However, it doesn't explicitly differentiate this tool from sibling tools like 'update_task' or 'list_tasks', which would be needed for a perfect score.

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 (e.g., 'update_task' for modifications, 'list_tasks' for retrieval). It also lacks prerequisites, such as required permissions or dependencies, leaving usage context unclear.

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