Skip to main content
Glama

create_project

Creates a TickTick project and returns its new ID, using a required name plus optional kind, color, and view mode.

Instructions

Create a TickTick project and return its new ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
nameYes
colorNoHex color such as #4772FA.
viewModeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare a non-destructive write (readOnlyHint=false, destructiveHint=false). The description adds one genuinely useful behavior beyond them: it returns the new project's ID, which matters since no output schema exists. It does not mention side effects, name-collision behavior, or whether the new project becomes active.

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?

A single front-loaded sentence with zero padding. Nothing is wasted, though the brevity is partly the source of the documentation gaps noted elsewhere.

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 four-parameter create tool with no output schema, the description covers the essential action and the return value, so an agent could make a minimal valid call with only the required `name`. It is not complete enough to explain the optional `kind`/`viewMode` enums or color formatting expectations, leaving meaningful gaps.

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

Parameters2/5

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

Schema coverage is only 25% — only `color` carries a description — and the tool description says nothing about any of the four parameters. The distinction between `kind` TASK and NOTE, the meaning of `viewMode`, or any defaults for optional fields are left entirely unexplained.

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 names a specific verb ("Create") and resource ("a TickTick project"), and the return value is stated. It is clearly distinguishable from get_project, update_project and delete_project by name, but the text itself does not explicitly contrast it with those siblings, which is why it stops short of 5.

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 on when to use this versus alternatives such as list_projects or get_project, and no prerequisites (e.g., whether the project name must be unique or which account it lands in). The only usable signal is the verb itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.