Skip to main content
Glama
hildersantos

Things MCP

by hildersantos
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

things_add_todo

Create new to-dos in Things 3 with checklists to break down complex tasks into manageable steps, schedule deadlines, and organize with tags and projects.

Instructions

Add a new to-do to Things with full support for checklists to break down complex tasks into manageable steps. Use checklist when task has multiple components that don't warrant a separate project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
notesNo
whenNoSchedule the todo: today/tomorrow/evening (relative), anytime/someday (Things categories), YYYY-MM-DD (specific date), or YYYY-MM-DD@HH:MM (specific time)
deadlineNo
tagsNo
checklist_itemsNoBreak down this todo into smaller, manageable steps using a checklist. Perfect for complex tasks that have multiple components but don't warrant a full project. Each checklist item can be individually checked off, providing visual progress feedback. Use when user mentions "steps", "checklist", "break down into parts", or when a task has multiple actionable components (e.g., "Plan event" → ["Book venue", "Arrange catering", "Send invites"]). Alternative to creating separate todos for multi-step tasks.
list_idNoID of the project or area to add the todo to
listNoName of the project, area, or built-in list (inbox, today, anytime, etc.)
headingNoPlace this todo under a specific heading within the project
completedNo
canceledNo

Implementation Reference

  • src/tools/add.ts:27-29 (handler)
    The handler implementation for the things_add_todo tool, which delegates to jsonBuilder.createTodo.
    if (toolName === 'things_add_todo') {
  const todoParams = params as z.infer<typeof AddTodoSchema>;
  return jsonBuilder.createTodo(todoParams);
  • src/tools/add.ts:14-18 (registration)
    Registration of the things_add_todo tool definition within the AddToolHandler.
    {
  name: 'things_add_todo',
  description: 'Add a new to-do to Things with full support for checklists to break down complex tasks into manageable steps. Use checklist when task has multiple components that don\'t warrant a separate project.',
  schema: AddTodoSchema
},

Tool Definition Quality

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It explains checklist behavior ('individually checked off', 'visual progress feedback') but omits other critical behavioral traits like error handling, idempotency, or what happens when both list_id and list are provided.

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?

Two sentences, both earning their place. The first establishes purpose and key feature; the second provides specific usage guidance. No redundancy or filler.

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 an 11-parameter creation tool with no annotations or output schema, the description is incomplete. While checklist functionality is well-covered, the lack of parameter documentation for deadline, completed flags, and heading leaves significant 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 coverage is low at 45%. The description elaborates on checklist usage patterns but fails to compensate for undocumented parameters like deadline (format?), completed/canceled (behavior when true?), or notes. Heavy focus on checklist_items leaves other parameters 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 clearly states the tool 'Add[s] a new to-do to Things' with a specific verb and resource. It distinguishes from things_add_project by noting checklists are for tasks that 'don't warrant a separate project,' though this differentiation could be more explicit.

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

Usage Guidelines3/5

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

Provides clear guidance on when to use the checklist feature ('when task has multiple components'), but lacks explicit guidance on when to use this tool versus siblings like things_add_project or things_update_todo. No mention of prerequisites or exclusions.

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/hildersantos/things-mcp'

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