Skip to main content
Glama

Save a list to MyGroceryPal

save_shopping_list
Idempotent

Add products to the user's MyGroceryPal shopping list, so they can open it in the app or on the web, and get deal alerts on items on the list the way their MyGroceryPal notification settings say. Only adds: a product already on the list is left as it is. Needs the user's MyGroceryPal account.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "items": "<items>"
    },
    "name": "save_shopping_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
storeNoThe store the user plans to buy these at, if one

Output Schema

NameRequiredDescriptionDefault
addedYes
listCountYes
addedCountYes
savedListUrlYes
alreadyOnListYes
alreadyOnListCountYes
notFoundProductIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / added
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "name": {
      +        "type": "string"
      +      },
      +      "productId": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "productId",
      +      "name"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / alreadyOnList
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "name": {
      +        "type": "string"
      +      },
      +      "productId": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "productId",
      +      "name"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / listCount
      Added value: +{
      +  "maximum": 9007199254740991,
      +  "minimum": -9007199254740991,
      +  "type": "integer"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "addedCount",
      -  "alreadyOnListCount",
      -  "notFoundProductIds",
      -  "savedListUrl"
      -]New value: +[
      +  "addedCount",
      +  "alreadyOnListCount",
      +  "notFoundProductIds",
      +  "savedListUrl",
      +  "added",
      +  "alreadyOnList",
      +  "listCount"
      +]
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=false), so the bar is lower. The description still adds real value by spelling out what idempotency means here ('a product already on the list is left as it is') and by noting the account requirement and the deal-alert side effect. It does not explain what happens to a supplied quantity for an existing item, which is the main behavioral ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The add action and its add-only semantics are front-loaded, and each of the three sentences carries information. The deal-alert sentence is somewhat long relative to its utility but is not filler.

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?

With an output schema present and rich annotations, the description need not document return values. It covers purpose, prerequisite, and the non-overwrite rule adequately. The remaining gap is how quantity and store are applied, particularly for items already on the list.

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 description coverage is 50%: store and the nested productId are documented inline, while the items array itself and quantity have no descriptions. The description adds only the loose notion that 'products' are supplied in a list and that duplicates are ignored; it says nothing about quantity, the 40-item cap, or the store parameter's effect. Baseline 3 for partial coverage.

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 opens with a specific verb and resource ('Add products to the user's MyGroceryPal shopping list') and states the user-visible outcome. It is clearly distinguishable from siblings like remove_saved_items or list_saved_items by the 'Only adds' clause, though it never names an alternative outright.

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?

It gives the reason to call it (list appears in app/web, triggers deal alerts) and a prerequisite (needs the user's MyGroceryPal account), which implies when it is appropriate. It never says when not to use it or points to search_grocery_prices / price_shopping_list as the way to obtain product IDs, so routing is only inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources