Skip to main content
Glama

create_chore

Create recurring chores that carry forward unfinished occurrences instead of resetting each period. Supports daily, every N days, or weekly recurrence with optional rolling or fixed cadence.

Instructions

Create a recurring chore that lingers until done.

Chores differ from habits in that an unfinished occurrence carries forward (Missed/InProgress) rather than resetting each period. complete_by should be the first scheduled date as ISO-8601. recurrence follows the same shape as Task: {"type": "daily"}, {"type": "every_n_days", "n": 3}, or {"type": "weekly", "days": ["Mon", "Wed"]}.

v0.2 optional fields:

  • cadence_mode: "rolling" (default; the next occurrence is computed from the actual completion time) or "fixed" (the next occurrence is anchored to the original schedule, ignoring completion delay).

  • deadline_time_of_day: "HH:MM" time-of-day deadline within scheduled_date (user's TZ). Defaults to end-of-day.

  • subtask_template: a list of subtask shapes that materialize as child Tasks on each occurrence. Empty list (default) means no template.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
descriptionNo
complete_byNo
recurrenceNo
parent_idNo
labelsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It explains core behavior (lingering, recurrence types, cadence_mode, deadline_time_of_day, subtask_template). Lacks details on error handling or failure modes.

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?

Well-structured: opening sentence, distinction from habits, recurrence format, then optional fields. Each sentence adds value, no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 6 parameters and recurrence complexity, the description covers core concept, usage context, parameter formats, and optional features. No annotations or output schema needed. Complete for an AI agent.

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

Parameters4/5

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

Schema description coverage is 0%. Description explains 'complete_by' format (ISO-8601), 'recurrence' shape, and optional fields (cadence_mode, deadline_time_of_day, subtask_template). Does not cover all parameters (e.g., parent_id, labels), but adds significant value.

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 it creates a recurring chore that 'lingers until done,' distinguishing it from habits. It specifies the verb 'Create' and resource 'chore' with explicit behavioral difference.

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

Usage Guidelines4/5

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

The description contrasts chores with habits, giving clear context for when to use this tool. However, it does not explicitly state when not to use or name alternative tools beyond the sibling list.

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