haus

update_shopping_list_item

Update a shopping list item's name, quantity, and/or category. Only the fields provided are changed; any field left out keeps its current value.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Item id from add_shopping_list_item or list_shopping_list_items.
`name`	No	New item name.
`category`	No	New store-aisle category, overriding the auto-assigned one.
`quantity`	No	New quantity, 1-9999. Replaces rather than adds to the current one.
`shoppingListId`	No	Move the item to a different list, an id from list_shopping_lists. Omit to leave it where it is; name the default list explicitly to move it back.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 8, 2026

changedInput schema / properties / category / description

Previous value: -"New store-aisle category for the item, overriding any auto-assigned category. Omit to leave the current category unchanged."New value: +"New store-aisle category, overriding the auto-assigned one."

changedInput schema / properties / id / description

Previous value: -"The ID of the shopping list item to update, as returned by add_shopping_list_item, batch_add_shopping_list_items, or list_shopping_list_items."New value: +"Item id from add_shopping_list_item or list_shopping_list_items."

changedInput schema / properties / name / description

Previous value: -"New name for the item. Maximum 200 characters. Omit to leave the current name unchanged."New value: +"New item name."

changedInput schema / properties / quantity / description

Previous value: -"New quantity for the item, replacing (not adding to) the current quantity. Minimum 1, maximum 9999. Omit to leave the current quantity unchanged."New value: +"New quantity, 1-9999. Replaces rather than adds to the current one."

addedInput schema / properties / shoppingListId

Added value: +{
+  "description": "Move the item to a different list, an id from list_shopping_lists. Omit to leave it where it is; name the default list explicitly to move it back.",
+  "examples": [
+    "0189c8d4f2b1712a9e4d6c9a1b2e3f4a"
+  ],
+  "type": "string"
+}

Changed9 schema fields changedJul 14, 2026

addedInput schema / examples

Added value: +[
+  {
+    "category": "DairyAndEggs",
+    "id": "0189c8d4f2b1712a9e4d6c9a1b2e3f4a",
+    "quantity": 3
+  }
+]

addedInput schema / properties / category / description

Added value: +"New store-aisle category for the item, overriding any auto-assigned category. Omit to leave the current category unchanged."

addedInput schema / properties / category / examples
```
Added value: +[
+  "DairyAndEggs"
+]
```

addedInput schema / properties / id / description

Added value: +"The ID of the shopping list item to update, as returned by add_shopping_list_item, batch_add_shopping_list_items, or list_shopping_list_items."

addedInput schema / properties / id / examples

Added value: +[
+  "0189c8d4f2b1712a9e4d6c9a1b2e3f4a"
+]

addedInput schema / properties / name / description

Added value: +"New name for the item. Maximum 200 characters. Omit to leave the current name unchanged."

addedInput schema / properties / name / examples
```
Added value: +[
+  "Whole milk"
+]
```

changedInput schema / properties / quantity / description

Previous value: -"Minimum: 1"New value: +"New quantity for the item, replacing (not adding to) the current quantity. Minimum 1, maximum 9999. Omit to leave the current quantity unchanged."

addedInput schema / properties / quantity / examples
```
Added value: +[
+  3
+]
```

First observedJun 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already flag this as a non-read-only, non-destructive mutation, and the description adds a useful behavioral trait: omitted fields retain their current values. This partial-update guarantee is not visible in the annotations. It does not mention move-to-another-list behavior, but that is covered by the schema.

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 verb/resource and ending with a precise semantic guarantee. No filler or repetition of schema details.

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 that all five parameters are fully described in the schema and an output schema exists, the description provides enough context for correct invocation. The missing usage alternatives and the unmentioned shoppingListId move capability are the only real gaps, but neither blocks an agent that reads the schema.

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 description coverage is 100%, so the baseline is 3. The description adds global partial-update semantics ('only the fields provided are changed') that the individual parameter descriptions do not fully convey, helping an agent understand how name, quantity, category, and shoppingListId interact.

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 names a specific verb ('Update') and resource ('shopping list item') and lists the main mutable fields, which is enough to distinguish it from add/remove/list/buy siblings. However, it omits the shoppingListId behavior (moving the item to a different list), so it under-describes the full scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The partial-update sentence implies this is the tool to use when changing selected fields without replacing the whole item. However, there is no explicit statement of when to use it versus add_shopping_list_item, buy_shopping_list_item, or remove_shopping_list_item, and no exclusions or prerequisites are stated.

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?