Skip to main content
Glama

create_chore

Create a chore with flexible repeat options, assign it to users or a circle, set due dates, add subtasks, labels, and configure reminders.

Instructions

Create a new chore. Use simple inputs like usernames and day names.

EXAMPLES:

  • Simple: {name: 'Take out trash', days_of_week: ['Mon','Thu'], time_of_day: '19:00', usernames: ['Alice']}

  • One-time: {name: 'Fix faucet', due_date: '2025-11-10', priority: 3}

  • With subtasks: {name: 'Weekly review', subtask_names: ['Check email','Update notes']}

If no usernames provided, chore is assigned to ANYONE in the circle (round-robin).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesChore name (required, 1-200 chars)
pointsNoPoints awarded on completion
due_dateNoDue date: YYYY-MM-DD or RFC3339
priorityNo0=unset, 1=lowest, 2=low, 3=medium, 4=highest
timezoneNoIANA timezone (default: America/New_York)
frequencyNoMultiplier (e.g., 2=biweekly). Default: 1
usernamesNoAssign by username/display name. First becomes primary assignee. If omitted, assigned to anyone.
is_privateNoVisible only to creator. Default: false
is_rollingNoNext due based on completion (true) vs fixed schedule (false). Default: false
descriptionNoChore description
label_namesNoLabels by name (e.g., ['cleaning','urgent']). Must exist first — use create_label.
time_of_dayNoTime in HH:MM format (e.g., '16:00')
days_of_weekNoDays as short names: ['Mon','Wed','Fri']. Auto-sets frequency_type to days_of_the_week.
subtask_namesNoChecklist items: ['Step 1','Step 2']
enable_naggingNoRepeated reminders until completed. Default: false
frequency_typeNoHow often it repeats (default: once). Use 'days_of_the_week' with days_of_week param for specific days.
assign_strategyNoHow to rotate assignment. Default: round_robin (when anyone) or least_completed (when specific users)
require_approvalNoRequire approval to mark complete. Default: false
remind_at_due_timeNoRemind exactly at due time. Default: false
remind_minutes_beforeNoRemind X minutes before due time
Behavior4/5

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

No annotations, so description covers default assignment, primary assignee from usernames, label prerequisite, and mentions default values for frequency, timezone. Does not discuss side effects like timers or approval flows beyond parameters.

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?

Front-loaded with purpose and examples. Well-organized but slightly lengthy due to parameter descriptions that are also in schema. Each part earns its place.

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?

For 20 parameters and no output schema, description covers key behaviors (assignment, rolling, labels, times). Missing explicit explanation of default values like is_private, but schema covers them. Adequate for an 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 coverage is 100%, so baseline is 3. Description adds value with examples showing combinations, clarifies behavior for usernames vs. default assignment, and explains label creation prerequisite.

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 chore' with a direct verb and resource. Examples and parameter details distinguish it from siblings like update_chore, complete_chore, etc.

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?

Provides examples and explains when to use which parameters (e.g., label_names must exist, use create_label). Includes behavior for omitted usernames. Lacks explicit when-not or alternatives to other tools.

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/danielrosehill/donetick-mcp'

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