Skip to main content
Glama

create_task

Create a new task with optional due date, parent task, labels, and recurrence patterns such as daily, weekly, or every N days.

Instructions

Create a new task.

complete_by must be an ISO-8601 UTC timestamp. parent_id attaches the new task as a child of an existing task. productive and desire are floats in [0, 1] representing how productive this task feels and how much the user wants to do it. recurrence sets a repeat schedule. Use {"type": "daily"}, {"type": "every_n_days", "n": 3}, or {"type": "weekly", "days": ["Mon", "Wed", "Fri"]}. recurring_type controls behavior when a recurring task is missed. Must be one of "chore" (lingers until done, default), "habit" (fresh start each day), or "event" (time-bound, can't be made up). Only meaningful when recurrence is set.

v0.2 optional field:

  • occurrence_id: when this Task is a materialized subtask of a recurring entity's occurrence, the Occurrence id it belongs to. Normal tasks omit this field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
descriptionYes
labelsNo
parent_idNo
assigneeNo
complete_byNo
productiveNo
desireNo
recurrenceNo
recurring_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description must cover behavior. It explains recurrence behavior and optional occurrence_id but does not mention auth requirements, side effects, or error conditions.

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?

Description is well-structured, front-loaded with purpose, then parameter details. Slightly verbose but justified given 10 parameters.

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?

Covers all parameters with meaningful detail. Has output schema (context hint). Lacks error handling or prerequisite info but is comprehensive for a creation tool.

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

Parameters5/5

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

Schema has 0% description coverage; description adds meanings for all parameters, including formats and examples for recurrence, complete_by, productive, desire, and recurring_type.

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?

The description clearly states 'Create a new task' and explains parameter purposes, distinguishing it from sibling tools like create_chore, create_event, create_habit.

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?

Does not explicitly state when to use create_task vs siblings. It implies context for occurrence_id but lacks when-to-use or when-not-to-use guidance.

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/Circuit-Stitch/defernowork-mcp'

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