List outstanding (unbought) shopping list items with their name, quantity, category and shoppingListId. Pass shoppingListId to limit it to one named list.
| Name | Required | Description | Default |
|---|---|---|---|
| shoppingListId | No | One named list, an id from list_shopping_lists. Omit for every list. |
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | ||
| title | No | ||
| message | No | ||
| variant | No |
Changes observed during successful MCP inspections.
Input schema / descriptionRemoved value: -"No parameters. Returns the active (not yet bought) items on the current household's shopping list."Input schema / examplesPrevious value: -[
- {}
-]New value: +[
+ {},
+ {
+ "shoppingListId": "0189c8d4f2b1712a9e4d6c9a1b2e3f4a"
+ }
+]Input schema / propertiesAdded value: +{
+ "shoppingListId": {
+ "description": "One named list, an id from list_shopping_lists. Omit for every list.",
+ "examples": [
+ "0189c8d4f2b1712a9e4d6c9a1b2e3f4a"
+ ],
+ "type": "string"
+ }
+}Input schema / descriptionAdded value: +"No parameters. Returns the active (not yet bought) items on the current household's shopping list."Input schema / examplesAdded value: +[
+ {}
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe-read nature is covered. The description adds behavioral context beyond annotations by specifying that only outstanding/unbought items are returned, which fields are included, and the optional list-scoping behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler. The first sentence front-loads the tool's core purpose and output, and the second provides the optional parameter behavior. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has a single optional parameter fully described in the schema, an output schema, and annotations covering read-only/destructive hints. The description adds the key unbought-items semantics and the optional filter, making it complete for an agent to select and invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema fully documents the single optional shoppingListId parameter. The description's 'Pass shoppingListId to limit it to one named list' largely restates the schema's 'Omit for every list' rather than adding new meaning, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: 'List outstanding (unbought) shopping list items'. It clearly distinguishes from sibling tools like list_shopping_lists (lists vs items) and add/buy/remove/update shopping list item operations. The mention of returned fields (name, quantity, category, shoppingListId) adds useful precision.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides clear usage guidance: pass shoppingListId to limit to one named list, and the schema explicitly says omit it for every list. This is sufficient for the tool's simple optional-filter behavior, though it does not explicitly name alternative tools or exclusion conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.