Skip to main content
Glama
ZH1754629545

TickTick/Dida365 MCP Server

by ZH1754629545

create_project

Create a new project in Dida365 task management with customizable name, color, view mode, type, and sort order to organize tasks or notes effectively.

Instructions

Create a new project in Dida365. Requires at least a project name. Can specify color, view mode, kind and sort order. Returns the created project details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the new project (required)
colorNoHex color code for the project (e.g., "#F18181")
sortOrderNoNumerical sort order value (default 0)
viewModeNoView mode: "list", "kanban", or "timeline"
kindNoProject type: "TASK" or "NOTE"

Implementation Reference

  • Implements the create_project tool by constructing a Project object from input arguments (name required, optional color, sortOrder, viewMode, kind) and posting it to the Dida365 API /project endpoint. Returns the API response as formatted text content.
    case "create_project": {
        const project: Project = {
            name: args.name as string,
            ...(args.color ? {color: args.color as string} : {}),
            ...(args.sortOrder ? {sortOrder: args.sortOrder as number} : 0),
            ...(args.viewMode ? {viewMode: args.viewMode as string} : {}),
            ...(args.kind ? {kind: args.kind as string} : {}),
        };
    
        const response: AxiosResponse = await dida365Api.post("/project", project);
    
        return {
            content: [
                {
                    type: "text",
                    text: `项目创建成功: ${JSON.stringify(response.data, null, 2)}`,
                },
            ],
        };
    }
  • Defines the tool metadata including name, description, and input schema for create_project, specifying required 'name' and optional properties like color, sortOrder, viewMode, kind.
    {
        name: "create_project",
        description: "Create a new project in Dida365. Requires at least a project name. Can specify color, view mode, kind and sort order. Returns the created project details.",
        inputSchema: {
            type: "object",
            properties: {
                name: {
                    type: "string",
                    description: "Name of the new project (required)",
                },
                color: {
                    type: "string",
                    description: 'Hex color code for the project (e.g., "#F18181")',
                },
                sortOrder:{
                    type:"integer",
                    description:"Numerical sort order value (default 0)"
                },
                viewMode:{
                    type:"string",
                    description:'View mode: "list", "kanban", or "timeline"'
                },
                kind:{
                    type:"string",
                    description:'Project type: "TASK" or "NOTE"'
                }
            },
            required: ["name"],
        },
    },
  • TypeScript interface defining the structure of a Project object, used in the create_project handler for type safety.
    interface Project {
        id?: string;
        name?: string;
        color?: string;
        sortOrder?: number;
        viewMode? : string;
        kind? :string;
        closed?:boolean;
        groupId?: string;
        permission?:string;
    
    
    
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the creation action and return of details, but doesn't address permissions needed, whether this is idempotent, rate limits, error conditions, or what format the 'created project details' will be in. 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 three concise sentences that each serve a purpose: stating the action, listing optional parameters, and describing the return. It's front-loaded with the core purpose. Minor improvement could be made by combining the second and third sentences for even tighter structure.

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?

For a creation tool with 5 parameters, 100% schema coverage, but no annotations and no output schema, the description does an adequate job. It covers the basic action and parameters but lacks depth on behavioral aspects like error handling, authentication needs, or response format details that would be helpful given the mutation nature of the tool.

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 fully documents all 5 parameters. The description adds minimal value by listing the optional parameters (color, view mode, kind, sort order) but doesn't provide additional semantic context beyond what's in the schema descriptions. This meets the baseline for high schema coverage.

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 ('Create a new project'), target resource ('in Dida365'), and distinguishes it from siblings like 'update_project_by_projectID' or 'get_projects'. It uses a precise verb+resource combination that leaves no ambiguity about the tool's function.

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 provides implied usage by stating 'Requires at least a project name', which suggests this is the primary tool for creating projects. However, it doesn't explicitly state when to use this versus alternatives like 'update_project_by_projectID' or provide any exclusion criteria or prerequisites beyond the name requirement.

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