haus

create_task

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

Input Schema

TableJSON Schema

Name	Required	Description
`notes`	No	Freeform notes about the task. Not for assignment info.
`title`	Yes	The task's title, e.g. 'Take out the recycling'. Required; max 200 characters.
`dueDate`	No	The date the task is due, in YYYY-MM-DD format.
`preparationDate`	No	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.
`assignedToMemberId`	No	The member ID of the household member. Get this from list_house_members.

Output Schema

TableJSON Schema

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

Schema Changelog

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

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.5/5.0

Behavior4/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 valuable behavioral context by stating 'starts unassigned and uncompleted' and 'only title is required', which are not evident from annotations. No contradiction with annotations.

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, front-loaded with the core action, no redundant information. Every clause contributes meaning: the action, the minimal requirement, the default state, and the follow-up tools.

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 simple create tool with 5 parameters (1 required) and an output schema, the description covers the essential usage and default behavior. No return value explanation is needed due to the output schema, and the follow-up tool references handle the task lifecycle adequately.

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 parameters are fully documented. The description adds semantic meaning by explaining the default assignment/completion state, which clarifies how omitting optional parameters behaves. This goes beyond the schema's field descriptions.

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 'Creates a new household task' with a specific verb and resource. It distinguishes from siblings like update_task and create_recurring_task by emphasizing the default state and subsequent modification tools. The intent is unambiguous.

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 explicitly names assign_task, update_task, and complete_task as follow-up tools, implying create_task is for new tasks only. It lacks an explicit exclusion of recurring tasks, which is a minor gap given create_recurring_task is a sibling, but the direction is 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

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

Need Help?