Skip to main content
Glama

Kroger

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Kroger Product Search

kroger_product_search
Read-onlyIdempotent

Search grocery products at Kroger-family supermarkets with real shelf prices, promo/sale prices, stock level, and aisle. Answers "how much does milk cost", "is X in stock", grocery price comparison. Give a zip_code (or location_id) to get store-specific prices; without one, only the national product catalog is returned (no prices). Example: kroger_product_search({ term: "whole milk", zip_code: "45202" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesProduct search term, e.g. "whole milk", "cage free eggs", "diet coke 12 pack"
brandNoOptional brand filter, e.g. "Kroger", "Organic Valley"
limitNoMax products to return, 1-50 (default 10)
_apiKeyNoOptional: your own Kroger API credentials as "client_id:client_secret" (free at developer.kroger.com)
zip_codeNoUS ZIP code — the nearest store is auto-selected so prices and stock appear
location_idNoExact store location_id from kroger_store_locator (overrides zip_code)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "term": "whole milk",
+    "zip_code": "45202"
+  },
+  {
+    "brand": "Organic Valley",
+    "location_id": "01400959",
+    "term": "cage free eggs"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds that it returns real-time shelf prices, promos, stock, and aisle; also clarifies that without location no prices are returned. This adds useful behavioral context beyond annotations.

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?

Three compact sentences plus an example; front-loaded with core function. Every sentence provides essential information with no redundancy.

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?

Given no output schema, the description adequately explains what is returned (prices, stock, aisle, catalog). Covers location dependency. Could hint at pagination or filtering, but the limit parameter is already in schema.

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 has 100% description coverage, so parameters are well-documented. Description reinforces the role of zip_code/location_id with an example but does not add significant new semantics beyond the schema.

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?

Clearly states it searches grocery products at Kroger-family supermarkets, listing returned data (prices, stock, aisle). Includes example query and specifies what questions it answers (cost, stock, price comparison). Differentiates from siblings by focusing on product search vs. store locator or product details.

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?

Provides clear context: use for searching products and getting prices; explains that without location only national catalog is returned. Gives explicit example. Does not directly name alternatives but implies when to use location parameters.

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

All Kroger toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources