haus

create_recurring_task

Create a recurring task. It generates task instances on a schedule, each with the reminders set in reminderOffsetMinutes.

Input Schema

TableJSON Schema

Name	Required	Description
`notes`	No	Notes copied to every generated instance.
`title`	Yes	Title given to every generated instance.
`endDate`	No	Inclusive last date, YYYY-MM-DD. Omit for open-ended.
`isUrgent`	No	Mark every task this series generates as urgent.
`startDate`	No	First date to generate from, YYYY-MM-DD. Defaults to today.
`cronExpression`	Yes	Interval as 'N Unit', Unit one of Day, Week, Month, Year, e.g. '2 Week'. Not cron syntax.
`maxOccurrences`	No	Cap on instances generated, applied even if endDate is not reached.
`preparationDays`	No	Legacy single reminder, days before each occurrence's due date, 0-365 (0 means none); use reminderOffsetMinutes instead. Ignored when reminderOffsetMinutes is sent.
`assigneeRotation`	No	A member id from list_house_members.
`reminderOffsetMinutes`	No	Reminder lead times, in minutes before each generated task's due date. Each value is whole hours, 60-1380 (1-23 hours), or whole days, a multiple of 1440 up to 40320 (4 weeks, the most for a repeating item); a week is 10080. Up to 5 values. A due date counts from 00:00 on that day, so 300 (5 hours) is 19:00 the evening before. Day and week reminders arrive at 19:00 on the earlier day; hour reminders arrive that many hours before, or up to 15 minutes earlier.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`title`	No
`message`	No
`variant`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 24, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "assigneeRotation": [
-      "7f3a9c2e1b4d8f6a0c5e3b7d9a1f4c6e",
-      "a1b2c3d4e5f60718293a4b5c6d7e8f90"
-    ],
-    "cronExpression": "2 Week",
-    "endDate": "2026-12-31",
-    "maxOccurrences": 26,
-    "notes": "Blue bin only",
-    "preparationDays": 1,
-    "startDate": "2026-08-01",
-    "title": "Take out the recycling"
-  }
-]New value: +[
+  {
+    "assigneeRotation": [
+      "7f3a9c2e1b4d8f6a0c5e3b7d9a1f4c6e",
+      "a1b2c3d4e5f60718293a4b5c6d7e8f90"
+    ],
+    "cronExpression": "2 Week",
+    "endDate": "2026-12-31",
+    "maxOccurrences": 26,
+    "notes": "Blue bin only",
+    "reminderOffsetMinutes": [
+      1440
+    ],
+    "startDate": "2026-08-01",
+    "title": "Take out the recycling"
+  }
+]

addedInput schema / properties / isUrgent

Added value: +{
+  "description": "Mark every task this series generates as urgent.",
+  "examples": [
+    true
+  ],
+  "type": "boolean"
+}

changedInput schema / properties / preparationDays / description

Previous value: -"Days before each due date to set that instance's preparation date. Clamped to today if it would be past."New value: +"Legacy single reminder, days before each occurrence's due date, 0-365 (0 means none); use reminderOffsetMinutes instead. Ignored when reminderOffsetMinutes is sent."

addedInput schema / properties / reminderOffsetMinutes

Added value: +{
+  "description": "Reminder lead times, in minutes before each generated task's due date. Each value is whole hours, 60-1380 (1-23 hours), or whole days, a multiple of 1440 up to 40320 (4 weeks, the most for a repeating item); a week is 10080. Up to 5 values. A due date counts from 00:00 on that day, so 300 (5 hours) is 19:00 the evening before. Day and week reminders arrive at 19:00 on the earlier day; hour reminders arrive that many hours before, or up to 15 minutes earlier.",
+  "examples": [
+    [
+      1440,
+      10080
+    ]
+  ],
+  "items": {
+    "description": "One lead time in minutes: whole hours 60-1380, or a multiple of 1440 for days.",
+    "examples": [
+      1440
+    ],
+    "maximum": 40320,
+    "minimum": 60,
+    "multipleOf": 60,
+    "type": "integer"
+  },
+  "maxItems": 5,
+  "type": "array",
+  "uniqueItems": true
+}

Changed10 schema fields changedSep 8, 2026

changedInput schema / properties / assigneeRotation / description

Previous value: -"Ordered list of household member IDs to round-robin through, one per generated instance. Entries that are no longer valid house members are skipped and that instance is left unassigned."New value: +"A member id from list_house_members."

changedInput schema / properties / assigneeRotation / items / description

Previous value: -"A household member ID (from list_house_members) taking a turn in the rotation."New value: +"Member ids round-robined one per instance. Ids that are no longer members are skipped, leaving that instance unassigned."

changedInput schema / properties / cronExpression / description

Previous value: -"Recurrence frequency expression in the format 'N Unit', e.g. '2 Week' for every two weeks. Unit must be exactly Day, Week, Month, or Year (case-sensitive). Despite the parameter name, this is not cron syntax."New value: +"Interval as 'N Unit', Unit one of Day, Week, Month, Year, e.g. '2 Week'. Not cron syntax."

changedInput schema / properties / endDate / description

Previous value: -"The last date instances are generated through (inclusive), in YYYY-MM-DD format. Omit for an open-ended schedule."New value: +"Inclusive last date, YYYY-MM-DD. Omit for open-ended."

changedInput schema / properties / maxOccurrences / description

Previous value: -"Maximum number of task instances to generate in total. Generation stops once this many instances have been created, even if endDate has not been reached."New value: +"Cap on instances generated, applied even if endDate is not reached."

changedInput schema / properties / notes / description

Previous value: -"Freeform notes copied to every generated task instance."New value: +"Notes copied to every generated instance."

addedInput schema / properties / notes / examples
```
Added value: +[
+  "Blue bin only"
+]
```

changedInput schema / properties / preparationDays / description

Previous value: -"Number of days before each occurrence's due date to set that instance's preparation date. Clamped to today if the computed date would be in the past."New value: +"Days before each due date to set that instance's preparation date. Clamped to today if it would be past."

changedInput schema / properties / startDate / description

Previous value: -"The date the schedule starts generating instances from, in YYYY-MM-DD format. Defaults to today if omitted."New value: +"First date to generate from, YYYY-MM-DD. Defaults to today."

changedInput schema / properties / title / description

Previous value: -"The recurring task's title. Used as the title for every generated task instance."New value: +"Title given to every generated instance."

Changed17 schema fields changedJul 14, 2026

addedInput schema / examples

Added value: +[
+  {
+    "assigneeRotation": [
+      "7f3a9c2e1b4d8f6a0c5e3b7d9a1f4c6e",
+      "a1b2c3d4e5f60718293a4b5c6d7e8f90"
+    ],
+    "cronExpression": "2 Week",
+    "endDate": "2026-12-31",
+    "maxOccurrences": 26,
+    "notes": "Blue bin only",
+    "preparationDays": 1,
+    "startDate": "2026-08-01",
+    "title": "Take out the recycling"
+  }
+]

changedInput schema / properties / assigneeRotation / description

Previous value: -"List of userIds for round-robin assignment"New value: +"Ordered list of household member IDs to round-robin through, one per generated instance. Entries that are no longer valid house members are skipped and that instance is left unassigned."

addedInput schema / properties / assigneeRotation / items / description

Added value: +"A household member ID (from list_house_members) taking a turn in the rotation."

addedInput schema / properties / assigneeRotation / items / examples
```
Added value: +[
+  "7f3a9c2e1b4d8f6a0c5e3b7d9a1f4c6e"
+]
```

changedInput schema / properties / cronExpression / description

Previous value: -"Cron expression for recurrence. Format: minute hour dayOfMonth month dayOfWeek"New value: +"Recurrence frequency expression in the format 'N Unit', e.g. '2 Week' for every two weeks. Unit must be exactly Day, Week, Month, or Year (case-sensitive). Despite the parameter name, this is not cron syntax."

addedInput schema / properties / cronExpression / examples
```
Added value: +[
+  "2 Week"
+]
```

changedInput schema / properties / endDate / description

Previous value: -"YYYY-MM-DD format"New value: +"The last date instances are generated through (inclusive), in YYYY-MM-DD format. Omit for an open-ended schedule."

addedInput schema / properties / endDate / examples
```
Added value: +[
+  "2026-12-31"
+]
```

addedInput schema / properties / maxOccurrences / description

Added value: +"Maximum number of task instances to generate in total. Generation stops once this many instances have been created, even if endDate has not been reached."

addedInput schema / properties / maxOccurrences / examples
```
Added value: +[
+  26
+]
```

addedInput schema / properties / notes / description

Added value: +"Freeform notes copied to every generated task instance."

addedInput schema / properties / preparationDays / description

Added value: +"Number of days before each occurrence's due date to set that instance's preparation date. Clamped to today if the computed date would be in the past."

addedInput schema / properties / preparationDays / examples
```
Added value: +[
+  1
+]
```

changedInput schema / properties / startDate / description

Previous value: -"YYYY-MM-DD format"New value: +"The date the schedule starts generating instances from, in YYYY-MM-DD format. Defaults to today if omitted."

addedInput schema / properties / startDate / examples
```
Added value: +[
+  "2026-08-01"
+]
```

addedInput schema / properties / title / description

Added value: +"The recurring task's title. Used as the title for every generated task instance."

addedInput schema / properties / title / examples

Added value: +[
+  "Take out the recycling"
+]

First observedJun 30, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations only indicate readOnlyHint=false and destructiveHint=false. The description adds useful behavioral context by stating that the tool generates task instances on a schedule and applies reminderOffsetMinutes to each. However, it does not disclose side effects like immediate instance creation, series editability, or unassigned instances from assigneeRotation.

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 with no filler. The core action is stated first, followed by the key behavioral detail about schedule and reminders. Every sentence earns its place.

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?

The description is adequate at a high level, and the rich schema plus output schema cover parameter and return details. However, for a 10-parameter tool with nuanced behaviors like assigneeRotation and legacy preparationDays, the description could add more context about series lifecycle or when to prefer this over create_task.

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 baseline is 3. The description mentions reminderOffsetMinutes specifically, but the schema already documents its meaning and constraints in detail. No additional parameter semantics are provided beyond what the schema offers.

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 states a specific verb and resource ('Create a recurring task') and adds the key behavior of generating task instances on a schedule. It is clearly distinct from create_task and create_recurring_calendar_event by resource type, though it does not explicitly name a sibling for differentiation.

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?

No guidance is given on when to use this tool versus alternatives such as create_task for one-off tasks or create_recurring_calendar_event for recurring calendar events. The description implies its use for recurring tasks but provides no explicit when/when-not conditions.

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

All haus tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?