Skip to main content
Glama

haus

by app.onehaus

create_recurring_task

Create a recurring task that automatically generates task instances on a schedule.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoFreeform notes copied to every generated task instance.
titleYesThe recurring task's title. Used as the title for every generated task instance.
endDateNoThe last date instances are generated through (inclusive), in YYYY-MM-DD format. Omit for an open-ended schedule.
startDateNoThe date the schedule starts generating instances from, in YYYY-MM-DD format. Defaults to today if omitted.
cronExpressionYesRecurrence 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.
maxOccurrencesNoMaximum number of task instances to generate in total. Generation stops once this many instances have been created, even if endDate has not been reached.
preparationDaysNoNumber 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.
assigneeRotationNoOrdered 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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
titleNo
messageNo
variantNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed17 schema fields changed
    • 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"
+]
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description is not required to restate that. It does add the behavioral detail that instance generation is automatic, but does not disclose potential side effects like validation failures or duplicate schedule handling. This is a modest addition beyond the annotations.

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?

The description is a single sentence that is front-loaded and contains no redundant words. It is concise and to the point, though it could arguably add a note about alternatives. It earns full marks for efficiency, but is slightly less informative than a two-sentence description with explicit guidance.

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?

Given the rich input schema and the presence of an output schema, the description does not need to explain return values or parameter details. It covers the core action and its primary side effect (automatic instance generation). It is slightly minimal, but adequate for a create tool with well-documented parameters.

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?

The input schema provides 100% coverage with detailed descriptions for all 8 parameters, so the description does not need to add parameter-specific semantics. The high-level mention of 'schedule' ties to cronExpression, startDate, and endDate, but the schema already explains these thoroughly. Baseline 3 is appropriate.

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 uses a specific verb and resource ('Create a recurring task') and clearly distinguishes it from single task creation by adding 'automatically generates task instances on a schedule.' This differentiates it from sibling tools like create_task and create_recurring_calendar_event.

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 implies when to use this tool (for tasks that repeat) by mentioning schedule-based generation. However, it does not explicitly name alternatives or state exclusions, such as 'for one-off tasks use create_task instead.' The context is clear but lacks explicit guidance.

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

All haus toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool targets a distinct resource and action, with clear descriptions separating similar-sounding tools like create_calendar_event vs create_recurring_calendar_event. Shopping list operations (add, buy, remove, update) are clearly delineated.

Naming Consistency5/5

All tools follow a verb_noun snake_case pattern: create_*, list_*, update_*, delete_*, get_*, etc. Even special operations like store_memory, recall_memory, and skip_recommendation fit the pattern.

Tool Count1/5

With 68 tools, this server vastly exceeds a reasonable scope; the instruction manual indicates 50+ tools is an extreme mismatch. The breadth suggests the server should be split into focused sub-servers (tasks, shopping, calendar, etc.) rather than a single monolithic interface.

Completeness5/5

The tool surface covers full CRUD/lifecycle for all major resources: tasks, shopping, calendar, contacts, documents, appliances, vehicles, pets, recipes, meal plans, subscriptions, and memories. Additional features like house review, weather, and profile round out the household management domain.

Resources