haus

create_task

Creates a new household task. Only title is required; the task starts unassigned and uncompleted. Set reminders with reminderOffsetMinutes. Use assign_task, update_task, or complete_task to change it afterward.

Input Schema

TableJSON Schema

Name	Required	Description
`notes`	No	Freeform notes. Not for assignment info.
`title`	Yes	Task title, e.g. 'Take out the recycling'.
`dueDate`	No	Due date, YYYY-MM-DD.
`isUrgent`	No	Mark the task urgent so it is shown first and highlighted.
`preparationDate`	No	Legacy single reminder date, YYYY-MM-DD; use reminderOffsetMinutes instead. Ignored when reminderOffsetMinutes is sent. Must be on or before dueDate, and needs dueDate.
`assignedToMemberId`	No	Member id from list_house_members.
`reminderOffsetMinutes`	No	Reminder lead times, in minutes before the due date. Each value is whole hours, 60-1380 (1-23 hours), or whole days, a multiple of 1440 up to 525600 (365 days); 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. Needs dueDate.

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: -[
-  {
-    "assignedToMemberId": "7f3a9c2e1b4d8f6a0c5e3b7d9a1f4c6e",
-    "dueDate": "2026-08-01",
-    "notes": "Blue bin only",
-    "preparationDate": "2026-07-30",
-    "title": "Take out the recycling"
-  }
-]New value: +[
+  {
+    "assignedToMemberId": "7f3a9c2e1b4d8f6a0c5e3b7d9a1f4c6e",
+    "dueDate": "2026-08-01",
+    "notes": "Blue bin only",
+    "reminderOffsetMinutes": [
+      1440,
+      10080
+    ],
+    "title": "Take out the recycling"
+  }
+]

addedInput schema / properties / isUrgent

Added value: +{
+  "description": "Mark the task urgent so it is shown first and highlighted.",
+  "examples": [
+    true
+  ],
+  "type": "boolean"
+}

changedInput schema / properties / preparationDate / description

Previous value: -"Preparation date, YYYY-MM-DD. Must not follow dueDate."New value: +"Legacy single reminder date, YYYY-MM-DD; use reminderOffsetMinutes instead. Ignored when reminderOffsetMinutes is sent. Must be on or before dueDate, and needs dueDate."

addedInput schema / properties / reminderOffsetMinutes

Added value: +{
+  "description": "Reminder lead times, in minutes before the due date. Each value is whole hours, 60-1380 (1-23 hours), or whole days, a multiple of 1440 up to 525600 (365 days); 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. Needs dueDate.",
+  "examples": [
+    [
+      1440,
+      10080
+    ]
+  ],
+  "items": {
+    "description": "One lead time in minutes: whole hours 60-1380, or a multiple of 1440 for days.",
+    "examples": [
+      1440
+    ],
+    "maximum": 525600,
+    "minimum": 60,
+    "multipleOf": 60,
+    "type": "integer"
+  },
+  "maxItems": 5,
+  "type": "array",
+  "uniqueItems": true
+}

Changed6 schema fields changedSep 8, 2026

changedInput schema / properties / assignedToMemberId / description

Previous value: -"The member ID of the household member. Get this from list_house_members."New value: +"Member id from list_house_members."

changedInput schema / properties / dueDate / description

Previous value: -"The date the task is due, in YYYY-MM-DD format."New value: +"Due date, YYYY-MM-DD."

changedInput schema / properties / notes / description

Previous value: -"Freeform notes about the task. Not for assignment info."New value: +"Freeform notes. Not for assignment info."

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

changedInput schema / properties / preparationDate / description

Previous value: -"The date to start preparing for the task, in YYYY-MM-DD format. Must be on or before the due date if both are set."New value: +"Preparation date, YYYY-MM-DD. Must not follow dueDate."

changedInput schema / properties / title / description

Previous value: -"The task's title, e.g. 'Take out the recycling'. Required; max 200 characters."New value: +"Task title, e.g. 'Take out the recycling'."

Changed9 schema fields changedJul 14, 2026

addedInput schema / examples

Added value: +[
+  {
+    "assignedToMemberId": "7f3a9c2e1b4d8f6a0c5e3b7d9a1f4c6e",
+    "dueDate": "2026-08-01",
+    "notes": "Blue bin only",
+    "preparationDate": "2026-07-30",
+    "title": "Take out the recycling"
+  }
+]

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

changedInput schema / properties / dueDate / description

Previous value: -"YYYY-MM-DD format"New value: +"The date the task is due, in YYYY-MM-DD format."

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

addedInput schema / properties / notes / description

Added value: +"Freeform notes about the task. Not for assignment info."

changedInput schema / properties / preparationDate / description

Previous value: -"YYYY-MM-DD format"New value: +"The date to start preparing for the task, in YYYY-MM-DD format. Must be on or before the due date if both are set."

addedInput schema / properties / preparationDate / examples
```
Added value: +[
+  "2026-07-30"
+]
```

addedInput schema / properties / title / description

Added value: +"The task's title, e.g. 'Take out the recycling'. Required; max 200 characters."

addedInput schema / properties / title / examples

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

First observedJun 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only rule out read-only and destructive semantics, so the description carries the behavioral load. It discloses the default creation state (unassigned, uncompleted), the minimum input needed, and how reminders are supplied via reminderOffsetMinutes—meaningful behavior beyond schema constraints.

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 tightly packed sentences with the most decision-relevant facts front-loaded. Every clause earns its place: what it creates, what is required, the default state, reminder mechanism, and post-creation alternatives.

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?

Given full schema coverage, an output schema, and annotations, the description supplies what structured data cannot: initial state and post-creation routing. Nothing essential for invoking the tool correctly is missing.

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 coverage is 100%, so the baseline applies. The description usefully highlights title as the only required field and reminderOffsetMinutes as the reminder mechanism, but it adds no detail that the rich property descriptions do not already provide.

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 names the operation precisely: 'Creates a new household task' and adds the core initial-state facts (unassigned, uncompleted). This makes the resource and action unambiguous and distinguishes it from follow-up mutation tools like assign_task and complete_task.

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?

It gives explicit lifecycle guidance: 'Only title is required' and 'Use assign_task, update_task, or complete_task to change it afterward' tells an agent when this tool is the right choice versus those later mutations. It does not explicitly contrast with create_recurring_task, but the guidance is otherwise clear.

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?