haus

add_shopping_list_item

Add one item to the shopping list. A new item gets a category from its name; if an unbought item of the same name exists, its quantity is increased instead of duplicating it.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Item name, e.g. 'Milk'. A new item gets a category from its name; a matching unbought item has its quantity increased instead.
`category`	No	Store-aisle category to use instead of auto-assigning one; the name is then kept exactly as given. Omit to auto-categorise. Ignored when merged into an existing item.
`quantity`	No	How many to add, 1-9999, default 1. Added to the existing quantity when merged.
`shoppingListId`	No	Target list, an id from list_shopping_lists. Omit for the default. Merging only happens within one list.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

addedInput schema / properties / category

Added value: +{
+  "description": "Store-aisle category to use instead of auto-assigning one; the name is then kept exactly as given. Omit to auto-categorise. Ignored when merged into an existing item.",
+  "enum": [
+    "FruitAndVegetables",
+    "Bakery",
+    "DeliAndPreparedFoods",
+    "MeatAndSeafood",
+    "DairyAndEggs",
+    "Frozen",
+    "PantryAndDryGoods",
+    "SnacksAndConfectionery",
+    "Beverages",
+    "HouseholdAndCleaning",
+    "HealthAndPersonalCare",
+    "BabyAndKids",
+    "PetSupplies",
+    "Online",
+    "Other"
+  ],
+  "examples": [
+    "DairyAndEggs"
+  ],
+  "type": "string"
+}

Changed3 schema fields changedSep 8, 2026

changedInput schema / properties / name / description

Previous value: -"The name of the item to add, e.g. 'Milk' or 'Paper towels'. Maximum 200 characters. For a brand-new item, a category is auto-assigned from the name. If an unbought item with a matching name is already on the list, its quantity is increased instead of creating a duplicate entry, and the existing item keeps its current category unchanged."New value: +"Item name, e.g. 'Milk'. A new item gets a category from its name; a matching unbought item has its quantity increased instead."

changedInput schema / properties / quantity / description

Previous value: -"How many of the item to add. Defaults to 1 if omitted. Minimum 1, maximum 9999. When merged into an existing unbought item, this is added to the existing quantity (capped at 9999)."New value: +"How many to add, 1-9999, default 1. Added to the existing quantity when merged."

addedInput schema / properties / shoppingListId

Added value: +{
+  "description": "Target list, an id from list_shopping_lists. Omit for the default. Merging only happens within one list.",
+  "examples": [
+    "0189c8d4f2b1712a9e4d6c9a1b2e3f4a"
+  ],
+  "type": "string"
+}

Changed5 schema fields changedJul 14, 2026

addedInput schema / examples

Added value: +[
+  {
+    "name": "Milk",
+    "quantity": 2
+  }
+]

addedInput schema / properties / name / description

Added value: +"The name of the item to add, e.g. 'Milk' or 'Paper towels'. Maximum 200 characters. For a brand-new item, a category is auto-assigned from the name. If an unbought item with a matching name is already on the list, its quantity is increased instead of creating a duplicate entry, and the existing item keeps its current category unchanged."

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

changedInput schema / properties / quantity / description

Previous value: -"Minimum: 1"New value: +"How many of the item to add. Defaults to 1 if omitted. Minimum 1, maximum 9999. When merged into an existing unbought item, this is added to the existing quantity (capped at 9999)."

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

First observedJun 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only provide readOnlyHint=false and destructiveHint=false, so the description carries the transparency burden. It discloses two non-obvious behaviors beyond those hints: a new item gets its category from the name, and an unbought item of the same name has its quantity increased instead of being duplicated. This is exactly the kind of behavioral context an agent needs and that the annotations do not supply.

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 with zero filler. The core action is front-loaded ('Add one item'), and the second sentence packs the important behavioral details without redundancy.

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?

For a 4-parameter tool with an output schema and detailed property descriptions, the definition plus schema fully cover the inputs and the key merge/categorization rules. The only notable omission is an explicit pointer to the batch sibling for multi-item additions, which is more a usage-guideline gap than a completeness one.

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 cross-parameter semantics that the property-level schema does not fully convey: quantity is added to an existing item when merged, category is ignored on merge, and name determines both auto-categorization and duplicate matching. This meaningfully supplements the structured schema.

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?

States a specific verb and resource: 'Add one item to the shopping list.' It also clarifies the two key behaviors (auto-categorization from name, quantity increase on duplicate) that distinguish it from siblings like batch_add_shopping_list_items, buy_shopping_list_item, and update_shopping_list_item.

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 phrase 'Add one item' implies a single-item operation, which hints at contrast with the sibling batch_add_shopping_list_items, but there is no explicit instruction like 'use batch for multiple items' or 'use update_shopping_list_item to change an existing item.' Usage context is present but is implied rather than stated, and no exclusions are given.

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?