Skip to main content
Glama
ZH1754629545

TickTick/Dida365 MCP Server

by ZH1754629545

complete_task

Mark tasks as completed in TickTick/Dida365 by providing task and project IDs. Updates task status and records completion timestamp to track progress.

Instructions

Mark a task as completed. Requires both task ID and project ID. Updates the task's status to completed and sets completion timestamp.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesThe ID of the task to mark as complete (required)
projectIdYesThe ID of the project containing the task (required)

Implementation Reference

  • Handler for complete_task tool: validates projectId and taskId, POSTs to Dida365 API /project/{projectId}/task/{taskId}/complete to mark task as completed, returns the response as text content.
    case "complete_task":{
        const taskId = args.taskId as string;
        const projectId = args.projectId as string;
        throwValidError(projectId,taskId);
    
        const response: AxiosResponse = await  dida365Api.post(`/project/${projectId}/task/${taskId}/complete`)
    
        return {
            content:[
                {
                    type:"text",
                    text: `任务更新: ${JSON.stringify(response.data, null, 2)}`
                }
            ]
        }
    }
  • Schema definition for complete_task tool in ListTools response, specifying input parameters taskId and projectId as required strings.
    {
        name: "complete_task",
        description: "Mark a task as completed. Requires both task ID and project ID. Updates the task's status to completed and sets completion timestamp.",
        inputSchema: {
            type: "object",
            properties: {
                taskId: {
                    type: "string",
                    description: "The ID of the task to mark as complete (required)",
                },
                projectId: {
                    type: "string",
                    description: "The ID of the project containing the task (required)"
                }
            },
            required: ["taskId","projectId"],
        },
    },
  • Helper function throwValidError used in complete_task handler to validate that projectId and taskId are provided.
    function throwValidError(projectId : string,taskId : string){
        if(!projectId&&!taskId) throw new McpError(ErrorCode.InvalidRequest,"projectId 和 taskId 为空")
        if(!projectId) throw new McpError(ErrorCode.InvalidRequest,"projectId 为空")
        if(!taskId) throw new McpError(ErrorCode.InvalidRequest,"taskId 为空")
    }
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 the mutation behavior ('Updates the task's status') and timestamp setting, but lacks details on permissions, side effects, error conditions, or response format, leaving significant 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 efficiently structured in two sentences: the first states purpose and prerequisites, the second details behavioral effects. Every sentence adds value with zero waste, making it front-loaded and appropriately sized.

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 mutation tool with no annotations and no output schema, the description is incomplete. It covers the basic action but lacks crucial context like error handling, permissions, return values, or how it differs from sibling tools, leaving the agent under-informed.

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 fully documents both parameters. The description adds no additional meaning beyond implying both IDs are required, matching the schema. 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.

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 ('Mark a task as completed') and resource ('task'), distinguishing it from siblings like 'update_task' or 'delete_task' by focusing on completion status changes rather than general updates or deletions.

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 like 'update_task' for partial updates or 'delete_task' for removal. It mentions required parameters but offers no context about appropriate use cases or exclusions.

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