Skip to main content
Glama
evalor
by evalor

Create Project

create_project

Create a new project to organize tasks. Specify a name and optionally set color, view mode, and type.

Instructions

Create a new project (清单/folder/list) for organizing tasks (任务).

WHEN TO USE:

  • User wants to create a new task list (新建清单), folder, or project

  • Organizing tasks into categories or areas (分类整理任务)

REQUIRED: name (project title/清单名称)

OPTIONAL:

  • color: Hex color code (颜色, e.g., '#F18181')

  • viewMode: 'list' (列表, default), 'kanban' (看板), or 'timeline' (时间线)

  • kind: 'TASK' (任务清单, default) for tasks, 'NOTE' (笔记清单) for notes

  • sortOrder: Position in project list (排序位置)

RETURNS: Created project with generated ID. Use this ID for subsequent task operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoProject type (类型): 'TASK' (任务清单) for tasks or 'NOTE' (笔记清单) for notes. Defaults to 'TASK'. Optional.
nameYesThe name of the project (清单名称, required)
colorNoProject color in hex format (颜色, e.g., '#F18181'). Optional.
viewModeNoView mode (视图模式): 'list' (列表), 'kanban' (看板), 'timeline' (时间线). Defaults to 'list'. Optional.
sortOrderNoSort order for the project (排序位置). Optional.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
kindNo
nameYes
colorNo
closedNo
groupIdNo
viewModeNo
sortOrderNo
permissionNo
Behavior3/5

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

No annotations provided, so description must cover behavioral traits. Mentions return value (project with ID) and that ID is needed for subsequent tasks. Does not disclose side effects, permissions, or idempotency. Adequate but not thorough.

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?

Well-structured with clear sections (WHAT, WHEN, REQUIRED, OPTIONAL, RETURNS). Concise, no wasted words, front-loaded with purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complexity: 5 params, 1 required, enums, output schema. Description covers usage, param details, and return value. Lacks mention of validation errors or edge cases, but sufficient for typical use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds value with Chinese translations, examples for color and viewMode, and explanation of sortOrder. Enhances usability beyond schema descriptions.

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?

Clearly states the action (create), resource (project), and purpose (organizing tasks). Distinguishes from sibling tools like create_task by specifying it creates a list/folder/project.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a 'WHEN TO USE' section with explicit scenarios (new task list, folder, organizing categories). Does not explicitly state when not to use or suggest alternatives, but context is clear.

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/evalor/Dida365MCP'

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