Skip to main content
Glama
Kroger MCP Server

Kroger MCP Server

by CupOfOwls

clear_current_cart

Clears local cart tracking to sync with your actual Kroger cart after you manually remove items. Use when local tracking is out of sync or after clearing your Kroger cart.

Instructions

Clear all items from the local cart tracking only.

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

Use this tool only when:

  1. The user has already cleared their Kroger cart through the app/website

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

  3. Or when the local tracking is out of sync with the actual cart

Returns: Dictionary confirming the local cart tracking was cleared

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clear_current_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.6/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 well by disclosing the critical limitation that it cannot remove items from the real Kroger cart. It also mentions the local-only side effect and return shape, though it does not discuss reversibility or confirmation behavior.

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 and the structure is easy to scan. There is some redundancy between the IMPORTANT paragraph and the numbered usage conditions, but it remains purposeful.

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

Completeness5/5

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

Given the local-versus-actual cart distinction, zero parameters, and an output schema, the description provides everything an agent needs to avoid a dangerous misinterpretation. It clearly states what is cleared, what is not cleared, and when to invoke it.

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?

The tool has zero parameters, so parameter semantics are inherently simple and the empty schema is sufficient. The description correctly adds no unnecessary parameter detail.

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?

The description states a specific verb and resource: clearing all items from local cart tracking. It immediately distinguishes the scope from the sibling remove_from_cart/actual Kroger cart behavior by saying it only affects local tracking and cannot change the app/website 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?

It gives explicit when-to-use conditions in a numbered list and warns against misuse by stating the user must clear the actual Kroger cart separately. This is unusually clear routing guidance for an agent.

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