Skip to main content
Glama
ZH1754629545

TickTick/Dida365 MCP Server

by ZH1754629545

get_task_by_projectId_and_taskId

Retrieve detailed task information from TickTick/Dida365 by specifying both project and task IDs. Get complete task data including title, content, status, due date, priority, and subtasks.

Instructions

Retrieve a specific task's details by providing both the project ID and task ID. Returns complete task information including title, content, status, due date, priority, and subtasks if any.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesThe ID of the project containing the task (required)
taskIdYesThe ID of the task to retrieve (required)

Implementation Reference

  • Handler for the 'get_task_by_projectId_and_taskId' tool. Validates input parameters, calls the Dida365 API to fetch the specific task, and returns the task details as formatted JSON text.
    case "get_task_by_projectId_and_taskId":{
        const params: Record<string, any> = {};
        if(!args.projectId||!args.taskId) throw new McpError(ErrorCode.InvalidRequest, "项目ID或任务ID为空")
        if (args.projectId) params.projectId = args.projectId;
        if (args.taskId) params.taskId = args.taskId;
        const response = await dida365Api.get(`/project/${params.projectId}/task/${params.taskId}`);
    
        return {
            content: [
                {
                    type: "text",
                    text: `任务: ${JSON.stringify(response.data, null, 2)}`,
                },
            ],
        };
    }
  • Input schema definition for the tool, specifying required string parameters projectId and taskId.
    inputSchema: {
        type: "object",
        properties: {
            projectId: {
                type: "string",
                description: "The ID of the project containing the task (required)"
            },
            taskId: {
                type: "string",
                description: "The ID of the task to retrieve (required)"
            }
        },
        required: ["projectId","taskId"]
    }
  • src/index.ts:138-155 (registration)
    Tool registration in the ListTools handler, defining name, description, and input schema.
    {
        name: "get_task_by_projectId_and_taskId",
        description: "Retrieve a specific task's details by providing both the project ID and task ID. Returns complete task information including title, content, status, due date, priority, and subtasks if any.",
        inputSchema: {
            type: "object",
            properties: {
                projectId: {
                    type: "string",
                    description: "The ID of the project containing the task (required)"
                },
                taskId: {
                    type: "string",
                    description: "The ID of the task to retrieve (required)"
                }
            },
            required: ["projectId","taskId"]
        }
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves details and lists return fields (title, content, status, due date, priority, subtasks), but doesn't cover aspects like error handling (e.g., what happens if IDs are invalid), authentication needs, rate limits, or whether it's a read-only operation. The description adds some value by specifying return fields, but gaps remain for a tool with no annotation coverage.

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 concise and well-structured: the first sentence states the purpose and required inputs, and the second sentence details the return information. Both sentences earn their place by providing essential context without redundancy or fluff.

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 no annotations, no output schema, and 2 parameters with full schema coverage, the description is moderately complete. It covers the purpose, inputs, and return fields, but lacks behavioral details (e.g., error handling, auth) and doesn't fully compensate for the absence of annotations. It's adequate for a simple retrieval tool but has clear gaps.

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%, with both parameters ('projectId' and 'taskId') clearly documented in the schema as required string IDs. The description adds minimal value beyond the schema by reiterating the need for both IDs but doesn't provide additional context like ID formats or examples. Baseline 3 is appropriate when the 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 tool's purpose: 'Retrieve a specific task's details by providing both the project ID and task ID.' It specifies the verb ('retrieve'), resource ('task's details'), and required identifiers. However, it doesn't explicitly differentiate from sibling tools like 'get_tasks_by_projectId' (which likely retrieves multiple tasks) or 'get_project_by_projectId' (which retrieves project details).

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 by stating 'by providing both the project ID and task ID,' suggesting it's for retrieving a single, specific task. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like 'get_tasks_by_projectId' (for multiple tasks) or 'get_project_by_projectId' (for project details), nor does it mention prerequisites 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