Skip to main content
Glama

create_task

Creates a new Lilt task in the To Do list and syncs it to all the user’s devices through iCloud.

Instructions

Create a new task in Lilt. It lands in 'To Do' and syncs to all the user's devices via iCloud.

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": {
      "title": "<title>"
    },
    "name": "create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNoDue date, YYYY-MM-DD.
notesNoOptional longer description.
titleYesThe task title — required.
projectNoExisting project name (see list_projects). Errors if it doesn't exist.
intervalNoRepeat every N units (e.g. 2 = every other week). Default 1.
priorityNoDefault 'none'.
weekdaysNoFor weekly: comma-separated days, e.g. 'mon,wed,fri'. Omit to repeat on the due date's weekday.
recurrenceNoMake the task repeat. Requires `due`. When completed, the next occurrence is created automatically.
monthly_anchorNoFor monthly: 'day' = same day-of-month (default), 'weekday' = same Nth weekday (e.g. 2nd Tuesday).
show_days_beforeNoHide the task from lists until this many days before it's due. Default: user's setting (usually 7).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/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 usefully discloses that the task lands in 'To Do' and syncs via iCloud, which is behavior beyond the schema, but it omits permissions, error behavior for invalid project names, and what the tool returns.

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 definition is two short sentences with the core action front-loaded and no filler. The secondary sentence adds behavioral context without padding.

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 create tool with ten parameters, the rich schema covers parameter semantics, and the description adds initial status and sync behavior. However, with no annotations and no output schema, it should say more about return values or error conditions to be complete.

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 input schema already documents all ten parameters, including recurrence anchoring and weekday formatting. The description adds no additional parameter meaning beyond the schema, which matches the baseline of 3 when schema coverage is high.

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 uses a specific verb and resource ('Create a new task in Lilt'), making the action unmistakable. It does not explicitly distinguish this from sibling mutation tools such as update_task or complete_task, but the creation semantics are clear.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The implied use case is obvious from 'create', but the description does not help an agent choose between this and update_task or complete_task.

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