Skip to main content
Glama

haus

by app.onehaus

update_task

Update task title, assignment, dates, or notes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe task's ID, as returned by create_task or list_tasks.
notesNoFreeform notes about the task. Not for assignment info. Omit to leave unchanged.
titleNoNew title for the task. Omit to leave unchanged; max 200 characters.
dueDateNoYYYY-MM-DD format, or empty string to clear. Omit to leave unchanged.
preparationDateNoYYYY-MM-DD format, or empty string to clear. Omit to leave unchanged.
assignedToMemberIdNoMember ID to assign, or empty string to unassign. Omit to leave the current assignment unchanged.

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. Changed11 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "dueDate": "2026-08-01",
+    "id": "018f2c9a1b2c7d3e9a4f5b6c7d8e9f0a",
+    "title": "Take out the recycling"
+  }
+]
    • changedInput schema / properties / assignedToMemberId / description
      Previous value: -"Member ID to assign, or empty string to unassign"New value: +"Member ID to assign, or empty string to unassign. Omit to leave the current assignment unchanged."
    • addedInput schema / properties / assignedToMemberId / examples
      Added value: +[
+  "7f3a9c2e1b4d8f6a0c5e3b7d9a1f4c6e"
+]
    • changedInput schema / properties / dueDate / description
      Previous value: -"YYYY-MM-DD format, or empty string to clear"New value: +"YYYY-MM-DD format, or empty string to clear. Omit to leave unchanged."
    • addedInput schema / properties / dueDate / examples
      Added value: +[
+  "2026-08-01"
+]
    • addedInput schema / properties / id / description
      Added value: +"The task's ID, as returned by create_task or list_tasks."
    • addedInput schema / properties / id / examples
      Added value: +[
+  "018f2c9a1b2c7d3e9a4f5b6c7d8e9f0a"
+]
    • changedInput schema / properties / notes / description
      Previous value: -"Freeform notes about the task. Not for assignment info."New value: +"Freeform notes about the task. Not for assignment info. Omit to leave unchanged."
    • changedInput schema / properties / preparationDate / description
      Previous value: -"YYYY-MM-DD format, or empty string to clear"New value: +"YYYY-MM-DD format, or empty string to clear. Omit to leave unchanged."
    • addedInput schema / properties / preparationDate / examples
      Added value: +[
+  "2026-07-30"
+]
    • addedInput schema / properties / title / description
      Added value: +"New title for the task. Omit to leave unchanged; max 200 characters."
  2. Changed2 schema fields changed
    • changedInput schema / properties / dueDate / description
      Previous value: -"YYYY-MM-DD format"New value: +"YYYY-MM-DD format, or empty string to clear"
    • changedInput schema / properties / preparationDate / description
      Previous value: -"YYYY-MM-DD format"New value: +"YYYY-MM-DD format, or empty string to clear"
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already disclose that this is a mutating (readOnlyHint=false) and non-destructive (destructiveHint=false) operation. The description adds the list of updatable fields, which gives some scope detail, but does not mention partial-update semantics or other behavioral nuances beyond what the schema already provides.

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?

The description is a single, front-loaded sentence with zero filler: 'Update task title, assignment, dates, or notes.' It efficiently communicates the core action and scope.

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 schema (100% property descriptions), the minimal annotations covering safety, and the presence of an output schema, the short description is largely sufficient. It could have mentioned partial-update behavior, but that is already documented in the parameter descriptions.

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% with clear descriptions for all six parameters. The description's field list ('title, assignment, dates, or notes') does not add meaning beyond the schema's per-property explanations, so the baseline of 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 ('update') with a clear resource ('task') and lists the exact fields (title, assignment, dates, notes), making its purpose unmistakable and distinguishing it from siblings like complete_task or delete_task.

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?

The description provides no guidance on when to use this tool versus alternatives like assign_task or complete_task. It only states what it does, with no mention of preferred scenarios, exclusions, or alternative tools.

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