Skip to main content
Glama
Kroger MCP Server

Kroger MCP Server

by CupOfOwls

remove_from_cart

Remove an item from local cart tracking to sync with changes made in the Kroger app or website; this does not modify your actual Kroger cart.

Instructions

Remove an item from the local cart tracking only.

IMPORTANT: This tool CANNOT remove items from the actual Kroger cart in the app/website. It only updates our local tracking to stay in sync. The user must remove the item from their actual cart through the Kroger app or website themselves.

Use this tool only when:

  1. The user has already removed an item from their Kroger cart through the app/website

  2. You need to update the local tracking to reflect that change

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": "remove_from_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
modalityNoSpecific modality to remove (if None, removes all instances)
product_idYesThe product ID to remove from the local tracking

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.4.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / modality / anyOf
      Added value: +[
      +  {
      +    "description": "How the order will be fulfilled: PICKUP or DELIVERY (uppercase)",
      +    "enum": [
      +      "PICKUP",
      +      "DELIVERY"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / modality / description
      Added value: +"Specific modality to remove (if None, removes all instances)"
    • removedInput schema / properties / modality / title
      Removed value: -"Modality"
    • removedInput schema / properties / modality / type
      Removed value: -"string"
    • addedInput schema / properties / product_id / description
      Added value: +"The product ID to remove from the local tracking"
    • addedInput schema / properties / product_id / minLength
      Added value: +1
    • removedInput schema / properties / product_id / title
      Removed value: -"Product Id"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does the most important part: it loudly discloses that the tool does NOT mutate the real Kroger cart and that the user must act externally. That is a non-obvious side-effect warning an agent would otherwise get wrong. It stops short of covering failure modes (e.g., product_id not present in local tracking) or whether removal is idempotent.

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 critical caveat is front-loaded in the second sentence and reinforced with a compact numbered list, which is appropriate for a high-misuse-risk tool. It is slightly repetitive ('The user must remove the item from their actual cart through the Kroger app or website themselves' restates the IMPORTANT block), costing a little tightness.

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 no explanation, and the one thing that would actually trip an agent up — confusing local tracking with the real cart — is covered thoroughly. Remaining gap is edge-case behavior: what happens when product_id isn't in local tracking, and whether modality=null removing 'all instances' succeeds silently.

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%, so both product_id and the modality enum/default are already fully documented in the schema. The description adds no parameter-level detail beyond the schema. Baseline 3 applies since the schema does the heavy lifting.

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 ('Remove an item from the local cart tracking only') and immediately delimits the scope with the negative case: it cannot touch the real Kroger cart. The local-tracking-vs-real-cart distinction is exactly what an agent needs to disambiguate this from the cart-mutating siblings like add_items_to_cart and clear_current_cart.

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

Usage Guidelines5/5

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

Provides an explicit, numbered 'Use this tool only when' list with two concrete preconditions (user already removed the item themselves; local tracking needs syncing). This is a genuine when/when-not gate, not an implication. It doesn't name sibling alternatives by name, but the precondition effectively excludes every other cart tool on its own.

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