dida365-agent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DIDA365_REGION | No | Switch between Dida365 (China) and TickTick (International). Set to 'CN' for Dida365 or leave empty for TickTick (default). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dida365_create_taskA | Create a task. Requires title and project_id. Note: repeat_flag (RRULE) requires start_date to be set. Args: column_id: Kanban column to place the task in (project must be kanban view). kind: TEXT (default), NOTE, or CHECKLIST. Set to CHECKLIST when passing items. sort_order: Display order; lower values appear first. items: Subtask list (for CHECKLIST kind). Each dict should contain at least "title" (required). Optional keys (camelCase): "status" (0=normal, 1=done), "sortOrder", "startDate", "isAllDay", "timeZone". |
| dida365_batch_create_tasksA | Batch create multiple tasks in one request. Each dict requires "title" and "projectId". Optional fields same as create_task. Returns {"id2etag": {...}, "id2error": {...}}. |
| dida365_batch_update_tasksB | Batch update multiple tasks in one request. Each dict requires "id" and "projectId". Only provided fields are changed. Returns {"id2etag": {...}, "id2error": {...}}. |
| dida365_update_taskB | Update a task. Only provided fields are changed; omitted fields remain unchanged. Args: column_id: Move the task to this kanban column (project must be kanban view). kind: TEXT, NOTE, or CHECKLIST. Set to CHECKLIST when passing items. sort_order: Display order; lower values appear first. items: Subtask list (for CHECKLIST kind). Each dict should contain at least "title" (required). Optional keys (camelCase): "status" (0=normal, 1=done), "sortOrder", "startDate", "isAllDay", "timeZone". |
| dida365_complete_taskC | Mark a task as completed. |
| dida365_batch_complete_tasksB | Mark multiple tasks in a project as completed. |
| dida365_delete_taskB | Permanently delete a task. This action cannot be undone. |
| dida365_get_taskC | Get a single task by ID. |
| dida365_get_task_by_idA | Get a task by ID without needing project_id. |
| dida365_move_taskC | Move a task between projects. |
| dida365_get_project_tasksB | Get all uncompleted tasks in a project. |
| dida365_filter_tasksC | Filter tasks across projects. All parameters are optional and combinable. Tags filter uses AND logic (tasks must match all specified tags). |
| dida365_get_completed_tasksA | Get completed tasks, optionally filtered by project and completion time range. |
| dida365_list_undone_tasksC | List undone tasks within a date range, optionally filtered by projects. |
| dida365_list_projectsA | List all projects. Call this first to discover project IDs for other operations. |
| dida365_get_projectC | Get project details by ID. |
| dida365_create_projectC | Create a project. view_mode: list|kanban|timeline. kind: TASK|NOTE. |
| dida365_update_projectC | Update a project. Only provided fields are changed. |
| dida365_delete_projectA | Permanently delete a project and all its tasks. This action cannot be undone. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| projects_resource | All projects. Auto-loaded as context so Agent knows available project IDs and names. |
TDQS
Scored across 19 tools
Two tools (get_task and get_task_by_id) appear to do the same thing, and several retrieval tools (get_project_tasks, filter_tasks, list_undone_tasks, get_completed_tasks) overlap in purpose, though descriptions offer some differentiation. An agent could still misselect among task-listing tools.
All names use snake_case with a consistent dida365_ prefix and verb_noun structure. Minor deviations like get_task_by_id and mixed get/list verbs for retrieval prevent a perfect score.
19 tools is on the heavy side for a task manager, and a few are redundant (e.g., get_task_by_id), pushing it into the borderline range. Batch variants are justified but the set could be trimmed.
Core project and task lifecycle (create, read, update, delete, complete, move) is covered, plus batch operations and filtering. Minor gaps exist in tag management and batch deletion, but agents can work around them.