Skip to main content
Glama
ZH1754629545

TickTick/Dida365 MCP Server

by ZH1754629545

create_task

Add new tasks to Dida365 with title, project assignment, due dates, priority levels, and detailed descriptions for organized task management.

Instructions

Create a new task in Dida365 with specified details including title, project ID, content, due date and priority. The task will be created under the specified project. Requires at least title and projectId. Returns the created task details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesThe title/name of the task (required)
projectIdYesThe ID of the project where this task belongs (required)
contentNoDetailed description/content of the task
dueDateNoDue date in ISO 8601 format (e.g., 2023-12-31T23:59:59Z)
priorityNoPriority level from 0 (none) to 5 (highest)

Implementation Reference

  • The handler function for the 'create_task' tool. It constructs a Task object from the input parameters (title, projectId required; content, dueDate, priority optional), sends a POST request to the Dida365 API endpoint '/task', and returns the response detailing the created task.
    case "create_task": {
        const task: Task = {
            title: args.title as string,
            projectId: args.projectId as string,
        };
    
        if (args.content) task.content = args.content as string;
        if (args.dueDate) task.dueDate = args.dueDate as string;
        if (args.priority !== undefined) task.priority = args.priority as number;
    
        const response: AxiosResponse = await dida365Api.post("/task", task);
    
        return {
            content: [
                {
                    type: "text",
                    text: `任务创建成功: ${JSON.stringify(response.data, null, 2)}`,
                },
            ],
        };
    }
  • Input schema definition for the 'create_task' tool, specifying the JSON object structure with required 'title' and 'projectId' fields, and optional 'content', 'dueDate', and 'priority' fields.
    inputSchema: {
        type: "object",
        properties: {
            title: {
                type: "string",
                description: "The title/name of the task (required)",
            },
            projectId: {
                type: "string",
                description: "The ID of the project where this task belongs (required)",
            },
            content: {
                type: "string",
                description: "Detailed description/content of the task",
            },
            dueDate: {
                type: "string",
                description: "Due date in ISO 8601 format (e.g., 2023-12-31T23:59:59Z)",
            },
            priority: {
                type: "number",
                description: "Priority level from 0 (none) to 5 (highest)",
            },
        },
        required: ["title", "projectId"],
    },
  • src/index.ts:108-137 (registration)
    Registration of the 'create_task' tool in the ListTools response handler. Includes the tool name, description, and input schema.
    {
        name: "create_task",
        description: "Create a new task in Dida365 with specified details including title, project ID, content, due date and priority. The task will be created under the specified project. Requires at least title and projectId. Returns the created task details.",
        inputSchema: {
            type: "object",
            properties: {
                title: {
                    type: "string",
                    description: "The title/name of the task (required)",
                },
                projectId: {
                    type: "string",
                    description: "The ID of the project where this task belongs (required)",
                },
                content: {
                    type: "string",
                    description: "Detailed description/content of the task",
                },
                dueDate: {
                    type: "string",
                    description: "Due date in ISO 8601 format (e.g., 2023-12-31T23:59:59Z)",
                },
                priority: {
                    type: "number",
                    description: "Priority level from 0 (none) to 5 (highest)",
                },
            },
            required: ["title", "projectId"],
        },
    },
  • TypeScript interface defining the structure of a Task object, used in the create_task handler for type safety.
    interface Task {
        id?: string;                     // Task identifier
        projectId?: string;              // Task project id
        title?: string;                  // Task title
        isAllDay?: boolean;              // All day
        completedTime?: string;          // Task completed time in "yyyy-MM-dd'T'HH:mm:ssZ"
        content?: string;                // Task content
        desc?: string;                   // Task description of checklist
        dueDate?: string;                // Task due date time in "yyyy-MM-dd'T'HH:mm:ssZ"
        items?: ChecklistItem[];         // Subtasks of Task
        priority?: 0 | 1 | 3 | 5 | number;        // Task priority: None:0, Low:1, Medium:3, High:5
        reminders?: string[];            // List of reminder triggers
        repeatFlag?: string;             // Recurring rules of task
        sortOrder?: number;              // Task sort order
        startDate?: string;              // Start date time in "yyyy-MM-dd'T'HH:mm:ssZ"
        status?: 0 | 2 | number;                  // Task completion status: Normal: 0, Completed: 2
        timeZone?: string;               // Task timezone
    }
Behavior2/5

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

With no annotations provided, the description carries full burden. It discloses that the tool creates a new task and returns details, but lacks information about authentication requirements, rate limits, error conditions, or whether the operation is idempotent. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 appropriately sized with two sentences that efficiently convey the core functionality and requirements. It's front-loaded with the main purpose, though the parameter listing could be slightly more concise. Every sentence serves a purpose without obvious waste.

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 this is a mutation tool with no annotations and no output schema, the description is moderately complete but has gaps. It covers the basic purpose and parameters but lacks details about authentication, error handling, and the structure of returned task details. The absence of output schema means the description should ideally explain return values more thoroughly.

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 all 5 parameters thoroughly. The description lists the parameters ('title, project ID, content, due date and priority') but doesn't add meaningful semantic context beyond what's in the schema descriptions. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Create a new task') and resource ('in Dida365'), specifying it will be created under a project. It distinguishes from siblings like 'create_project' by focusing on tasks, but doesn't explicitly differentiate from 'update_task' or other task-related tools beyond the creation aspect.

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?

The description implies usage for creating tasks with specific details and mentions required parameters, but doesn't provide explicit guidance on when to use this versus alternatives like 'update_task' or 'complete_task'. It states 'Requires at least title and projectId', which gives some context but lacks comprehensive when/when-not instructions.

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/ZH1754629545/dida365-mcp-servers'

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