Skip to main content
Glama
Kroger MCP Server

Kroger MCP Server

by CupOfOwls

view_current_cart

Display items currently tracked in the local MCP cart and view a summary; this reflects only products added through the server, not your actual Kroger cart.

Instructions

View the current cart contents tracked locally.

Note: This tool can only see items that were added via this MCP server. The Kroger API does not provide permission to query the actual user cart contents.

Returns: Dictionary containing current cart items and summary

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": "view_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.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It does this well by disclosing that only items added through this MCP server are visible and that the Kroger API does not permit querying the actual user cart. It does not explicitly state read-only behavior or side-effect absence, but 'View' strongly implies it.

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?

The description is short, front-loaded with the core purpose, and separates the important limitation into a clear note. The returns summary is slightly redundant given the output schema, but it is brief and does not bloat the definition.

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?

For a zero-parameter read tool with an output schema, the description supplies the key missing context: the cart is locally tracked and cannot reflect the actual Kroger cart. That is enough for an agent to call it correctly and interpret the results.

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 not applicable in the usual sense. The baseline for zero-parameter tools is 4, and the description does not need to explain inputs.

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 gives a specific verb and resource: view the current cart contents. It also immediately clarifies that this is a locally tracked cart, not the user's actual Kroger cart, which distinguishes it from any tool that would query real account data.

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?

Usage is implied by 'View the current cart contents,' but the description does not explicitly say when to use this versus add_items_to_cart, remove_from_cart, clear_current_cart, or mark_order_placed. The local-only caveat is useful context, but it is a limitation rather than an alternative-selection guide.

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