Skip to main content
Glama

create_project

Create new projects or lists in Dida365 to organize tasks and manage workflows. Specify project name and optional color for visual categorization.

Instructions

创建新的项目(清单)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes项目名称
colorNo项目颜色(可选,如 '#FF6347')

Implementation Reference

  • The actual implementation of the 'create_project' tool which performs the HTTP POST request to the Dida365 Open API.
    def create_project(
        self,
        name: str,
        color: Optional[str] = None,
        view_mode: Optional[str] = None,
        folder_id: Optional[str] = None,
    ) -> Dict:
        """创建新项目(清单)"""
        data: Dict[str, Any] = {"name": name}
        if color:
            data["color"] = color
        if view_mode:
            data["viewMode"] = view_mode
        if folder_id:
            data["folderId"] = folder_id
    
        response = self.client.post("/project", json=data)
        response.raise_for_status()
        return response.json()
  • Tool definition schema for 'create_project'.
        "name": "create_project",
        "description": "创建新的项目(清单)。",
        "inputSchema": {
            "type": "object",
            "properties": {
                "name": {"type": "string", "description": "项目名称"},
                "color": {
                    "type": "string",
                    "description": "项目颜色(可选,如 '#FF6347')",
                },
            },
            "required": ["name"],
        },
    },
  • Dispatch logic for 'create_project' which calls the client implementation.
    elif name == "create_project":
        project = client.create_project(
            name=args["name"],
            color=args.get("color"),
        )
        return "✅ 项目创建成功!\n\n%s" % format_project(project)
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. It states it creates a new project but doesn't disclose behavioral traits such as permissions needed, whether it's idempotent, what happens on failure, or what the response looks like (since no output schema exists). This is inadequate for a mutation tool with zero 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 a single, efficient sentence in Chinese with no wasted words. It's front-loaded with the core action ('创建新的项目'), making it easy to parse quickly.

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?

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks critical information about behavior, error handling, and response format, which are essential for an agent to use it correctly. The high schema coverage doesn't compensate for these 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%, so the schema already documents both parameters ('name' and 'color'). The description doesn't add any meaning beyond what the schema provides (e.g., no examples, constraints, or usage tips for parameters). 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 verb ('创建新的' meaning 'create new') and resource ('项目' meaning 'project'), with '清单' (list/inventory) providing additional context. It distinguishes from siblings like 'delete_project' or 'get_projects', though it doesn't explicitly contrast with them.

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?

No guidance is provided on when to use this tool versus alternatives. While the purpose is clear, there's no mention of prerequisites, when not to use it, or how it relates to sibling tools like 'create_task' or 'get_projects'.

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/Martinqi826/dida-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server