Kroger MCP Server

Overview Schema Source Related Servers Discussions Admin

bulk_add_to_cart

Add multiple grocery items to a Kroger cart in one request, with quantity and pickup or delivery modality for each item.

Instructions

Add multiple items to the user's Kroger cart in a single operation.

If the user doesn't specifically indicate a preference for pickup or delivery, you should ask them which modality they prefer before calling this tool.

Input Schema

Name	Required	Description	Default
`items`	Yes	List of items to add. Each item should have: - product_id: The product ID or UPC - quantity: Quantity to add (default: 1) - modality: PICKUP or DELIVERY (default: PICKUP)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.4.0Oct 27, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / items / description

Added value: +"List of items to add. Each item should have:\n   - product_id: The product ID or UPC\n   - quantity: Quantity to add (default: 1)\n   - modality: PICKUP or DELIVERY (default: PICKUP)"

changedInput schema / properties / items / items / additionalProperties
```
Previous value: -trueNew value: +false
```
addedInput schema / properties / items / items / description
```
Added value: +"One item of a bulk_add_to_cart call"
```

addedInput schema / properties / items / items / properties

Added value: +{
+  "modality": {
+    "default": "PICKUP",
+    "description": "How the order will be fulfilled: PICKUP or DELIVERY (uppercase)",
+    "enum": [
+      "PICKUP",
+      "DELIVERY"
+    ],
+    "type": "string"
+  },
+  "product_id": {
+    "description": "13-digit productId or UPC, for example 0001111041700. Get one from search_products.",
+    "pattern": "^[0-9]{13}$",
+    "type": "string"
+  },
+  "quantity": {
+    "default": 1,
+    "description": "Quantity to add, 1 or more",
+    "minimum": 1,
+    "type": "integer"
+  }
+}

addedInput schema / properties / items / items / required
```
Added value: +[
+  "product_id"
+]
```
addedInput schema / properties / items / minItems
```
Added value: +1
```
removedInput schema / properties / items / title
```
Removed value: -"Items"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedAug 15, 2025

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It correctly implies a cart mutation and adds the useful modality-consultation rule, but says nothing about partial-failure behavior (if item 5 of 10 fails), whether items merge with or replace existing cart contents, or any auth/permission requirements.

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 short sentences, zero repetition, and the core capability is front-loaded ahead of the conditional guidance. Nothing could be cut without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the single nested items parameter is fully documented in the schema. However, for a mutation tool with no annotations, the description should say more about bulk-operation semantics such as partial success and cart-state effects.

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 100%, with each field (product_id pattern, quantity minimum, modality enum) already documented, so the baseline is 3. The description only restates that items are a list and reinforces the modality choice at a conversational level rather than adding new field semantics.

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?

States a specific verb (add), resource (Kroger cart), and scope (multiple items in a single operation), which implicitly separates it from the single-item sibling add_items_to_cart. The sibling is never named, so the differentiation is inferential rather than explicit.

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

Usage Guidelines4/5

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

Gives a concrete pre-call protocol: if the user has no stated preference, ask about pickup vs delivery before invoking. It does not cover when to prefer this over add_items_to_cart or what to do if only one item needs adding, so alternatives are left implied.

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