Skip to main content
Glama

add_project

Create new projects in Things 3 with title, notes, deadlines, tags, areas, and subtasks to organize tasks effectively.

Instructions

创建新的项目。支持标题、备注、区域、标签、子任务等。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo项目标题
notesNo备注内容
whenNo时间安排: today, tomorrow, evening, anytime, someday, 日期或日期时间
deadlineNo截止日期(yyyy-mm-dd)
tagsNo标签,逗号分隔
areaIdNo区域ID
areaNo区域标题
todosNo子待办事项列表
completedNo是否标记为完成
canceledNo是否标记为取消
revealNo是否导航进入项目

Implementation Reference

  • The handler function that implements the core logic of the 'add_project' tool. It builds a Things URL scheme using the provided arguments and opens it to trigger project creation in the Things app.
    async handleAddProject(args) {
      const url = buildThingsUrl('add-project', args);
      await this.openThingsUrl(url);
    
      return {
        content: [
          {
            type: 'text',
            text: `✅ 项目创建命令已发送${args.title ? `: ${args.title}` : ''}`,
          },
        ],
      };
    }
  • Input schema defining the parameters accepted by the 'add_project' tool, including title, notes, scheduling, tags, area, subtasks, and flags.
    inputSchema: {
      type: 'object',
      properties: {
        title: {
          type: 'string',
          description: '项目标题',
        },
        notes: {
          type: 'string',
          description: '备注内容',
        },
        when: {
          type: 'string',
          description: '时间安排: today, tomorrow, evening, anytime, someday, 日期或日期时间',
        },
        deadline: {
          type: 'string',
          description: '截止日期(yyyy-mm-dd)',
        },
        tags: {
          type: 'string',
          description: '标签,逗号分隔',
        },
        areaId: {
          type: 'string',
          description: '区域ID',
        },
        area: {
          type: 'string',
          description: '区域标题',
        },
        todos: {
          type: 'array',
          items: { type: 'string' },
          description: '子待办事项列表',
        },
        completed: {
          type: 'boolean',
          description: '是否标记为完成',
        },
        canceled: {
          type: 'boolean',
          description: '是否标记为取消',
        },
        reveal: {
          type: 'boolean',
          description: '是否导航进入项目',
        },
      },
    },
  • src/index.js:117-170 (registration)
    Registers the 'add_project' tool in the ListToolsRequestSchema handler, providing name, description, and input schema.
    {
      name: 'add_project',
      description: '创建新的项目。支持标题、备注、区域、标签、子任务等。',
      inputSchema: {
        type: 'object',
        properties: {
          title: {
            type: 'string',
            description: '项目标题',
          },
          notes: {
            type: 'string',
            description: '备注内容',
          },
          when: {
            type: 'string',
            description: '时间安排: today, tomorrow, evening, anytime, someday, 日期或日期时间',
          },
          deadline: {
            type: 'string',
            description: '截止日期(yyyy-mm-dd)',
          },
          tags: {
            type: 'string',
            description: '标签,逗号分隔',
          },
          areaId: {
            type: 'string',
            description: '区域ID',
          },
          area: {
            type: 'string',
            description: '区域标题',
          },
          todos: {
            type: 'array',
            items: { type: 'string' },
            description: '子待办事项列表',
          },
          completed: {
            type: 'boolean',
            description: '是否标记为完成',
          },
          canceled: {
            type: 'boolean',
            description: '是否标记为取消',
          },
          reveal: {
            type: 'boolean',
            description: '是否导航进入项目',
          },
        },
      },
    },
  • src/index.js:429-430 (registration)
    Dispatches 'add_project' tool calls to the handleAddProject method in the CallToolRequestSchema handler.
    case 'add_project':
      return await this.handleAddProject(args);
  • Helper function used by the handler to construct the Things URL scheme for the 'add-project' command, including parameter mapping and encoding.
    export function buildThingsUrl(command, params = {}) {
      const baseUrl = `things:///${command}`;
      const queryString = buildQueryString(params);
    
      if (!queryString) {
        return baseUrl;
      }
    
      return `${baseUrl}?${queryString}`;
    }
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 states this creates a new project but doesn't mention required permissions, whether creation is reversible, what happens on success/failure, or any side effects. For a creation tool with 11 parameters and no annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence that immediately states the core purpose. It's appropriately sized and front-loaded with the main action. However, the list of supported fields could be more structured, and it lacks any separation between required and optional parameters.

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?

For a project creation tool with 11 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what a 'project' represents in this system, how it differs from a 'todo', what happens after creation, or what the response contains. The agent lacks critical context for proper tool selection and invocation.

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 all 11 parameters thoroughly. The description lists some parameter categories (title, notes, area, tags, subtasks) but doesn't add meaningful semantics beyond what's in the schema. This meets the baseline for high schema coverage.

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 ('创建新的' - create new) and resource ('项目' - project), making the purpose explicit. It also lists supported fields (title, notes, area, tags, subtasks), which helps distinguish it from simpler creation tools. However, it doesn't explicitly differentiate from sibling tools like 'add_todo' or 'update_project'.

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. There's no mention of prerequisites, when to choose 'add_project' over 'add_todo' or 'update_project', or any context about project lifecycle. The agent must infer usage from the tool name alone.

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/Mieluoxxx/things_mcp'

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