Skip to main content
Glama
Kroger MCP Server

Kroger MCP Server

by CupOfOwls

add_items_to_cart

Add a single item to a Kroger cart with quantity and pickup/delivery option, tracking it locally for the user's order.

Instructions

Add a single item to the user's Kroger cart and track it locally.

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.

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": {
      "product_id": "<product_id>"
    },
    "name": "add_items_to_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
modalityNoHow the order will be fulfilled: PICKUP or DELIVERY (uppercase)PICKUP
quantityNoQuantity to add, 1 or more
product_idYes13-digit productId or UPC, for example 0001111041700. Get one from search_products.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.4.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / modality / description
      Added value: +"How the order will be fulfilled: PICKUP or DELIVERY (uppercase)"
    • addedInput schema / properties / modality / enum
      Added value: +[
      +  "PICKUP",
      +  "DELIVERY"
      +]
    • removedInput schema / properties / modality / title
      Removed value: -"Modality"
    • addedInput schema / properties / product_id / description
      Added value: +"13-digit productId or UPC, for example 0001111041700. Get one from search_products."
    • addedInput schema / properties / product_id / pattern
      Added value: +"^[0-9]{13}$"
    • removedInput schema / properties / product_id / title
      Removed value: -"Product Id"
    • addedInput schema / properties / quantity / description
      Added value: +"Quantity to add, 1 or more"
    • addedInput schema / properties / quantity / minimum
      Added value: +1
    • removedInput schema / properties / quantity / title
      Removed value: -"Quantity"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden. It reveals a useful behavioral trait — the item is also tracked locally, and the modality decision must be confirmed first — but it does not state auth prerequisites, behavior on duplicate entries, or whether the cart mutation is reversible.

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, action first, precondition second. No filler and nothing buried.

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?

An output schema exists, so return values need not be explained, and the schema fully documents the three parameters. The description covers the key pre-call decision (modality) but says nothing about authentication state or the local-tracking side effect's implications across sessions.

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 coverage is 100%, so the baseline is 3. The description earns a bump by clarifying that modality should be confirmed with the user rather than silently defaulted to PICKUP, which is meaningful guidance beyond the schema's enum and default.

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 and resource ('Add a single item to the user's Kroger cart') plus a scope qualifier ('single item') that implicitly separates it from bulk_add_to_cart. It never names the bulk sibling explicitly, so an agent must infer the distinction from the word 'single'.

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 prerequisite: ask the user about pickup vs delivery before calling when no preference is stated. That is real when-to-use guidance. The one gap is that it never says when to prefer bulk_add_to_cart for multiple items.

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