Skip to main content
Glama
ZH1754629545

TickTick/Dida365 MCP Server

by ZH1754629545

get_project_by_projectId

Retrieve detailed project information including name, color, view mode, kind, and sort order by providing the project ID from TickTick/Dida365 task management systems.

Instructions

Get detailed information about a specific project by its ID. Returns project metadata including name, color, view mode, kind and sort order.

Input Schema

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

Implementation Reference

  • Inline handler for the 'get_project_by_projectId' tool. Extracts projectId from args, validates it using throwValidError, calls dida365Api.get(`/project/${projectId}`), and returns the response as formatted text content.
    case "get_project_by_projectId":{
        const projectId = args.projectId as string;
        throwValidError(projectId,"1");
        const response: AxiosResponse = await  dida365Api.get(`project/${projectId}`);
        return {
            content:[
                {
                    type:"text",
                    text: `获取project成功: ${JSON.stringify(response.data, null, 2)}`
                }
            ]
        }
    }
  • Tool schema definition including name, description, and inputSchema with required 'projectId' string parameter. This is part of the tools list returned by ListToolsRequestHandler.
        name: "get_project_by_projectId",
        description: "Get detailed information about a specific project by its ID. Returns project metadata including name, color, view mode, kind and sort order.",
        inputSchema: {
            type: "object",
            properties: {
                projectId: {
                    type: "string",
                    description: "The ID of the project to retrieve (required)"
                }
            },
            required: ["projectId"]
        }
    },
  • Helper function used for input validation in the handler. Called with projectId and dummy taskId "1" to validate that projectId is 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 for behavioral disclosure. It mentions the return format ('project metadata including name, color, view mode, kind and sort order'), which is helpful, but doesn't address important behavioral aspects like error conditions (e.g., what happens if projectId is invalid), authentication requirements, rate limits, or whether this is a read-only operation (though implied by 'Get').

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 concise with two sentences: one stating the purpose and one detailing the return format. It's front-loaded with the core function. While efficient, it could be slightly more structured by explicitly separating purpose from output details.

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 simple read operation with 1 parameter and no output schema, the description is adequate but has gaps. It explains what information is returned, which compensates for the missing output schema, but doesn't cover error handling or behavioral constraints. Given the low complexity, it's minimally viable but not comprehensive.

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 the single parameter 'projectId' fully documented in the schema. The description adds no additional parameter semantics beyond what's in the schema (e.g., format examples, validation rules). This meets the baseline of 3 when schema coverage is high.

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 verb 'Get' and resource 'detailed information about a specific project by its ID', making the purpose unambiguous. It distinguishes from siblings like get_projects (which lists multiple projects) and get_task_by_projectId_and_taskId (which retrieves tasks). However, it doesn't explicitly contrast with these siblings in the text.

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 get_projects (for listing all projects) or get_task_by_projectId_and_taskId (for retrieving tasks within a project). It simply states what the tool does without contextual usage 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