Kroger MCP Server

Overview Schema Source Related Servers Discussions Admin

get_product_details

Retrieve detailed information for a specific Kroger product using its 13-digit UPC or product ID, with an optional store location for localized details.

Instructions

Get detailed information about a specific product.

Input Schema

Name	Required	Description	Default
`product_id`	Yes	13-digit productId or UPC, for example 0001111041700. Get one from search_products.
`location_id`	No	8-character store locationId, for example 01400513. Defaults to the preferred location set with set_preferred_location.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.4.0Oct 27, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / location_id / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "pattern": "^[A-Za-z0-9]{8}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / location_id / description

Added value: +"8-character store locationId, for example 01400513. Defaults to the preferred location set with set_preferred_location."

removedInput schema / properties / location_id / title
```
Removed value: -"Location Id"
```

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"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedAug 15, 2025

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. "Get" implies a read, but the description says nothing about authentication, error behavior when a product is missing, or the effect of the default location.

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?

It is a single front-loaded sentence with no wasted words. The brevity is appropriate structurally, even though the content is sparse.

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

Completeness3/5

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

The tool is a simple two-parameter read, the schema is fully documented, and an output schema exists, so return values need not be described. However, the description does not clarify what "detailed information" includes beyond what the output schema may show, leaving some contextual ambiguity.

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 coverage is 100%, and the schema already explains the 13-digit product ID, its relationship to search_products, and the default location behavior. The description adds no parameter meaning beyond that baseline.

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 clear verb and resource ("Get detailed information about a specific product"), so the agent knows this retrieves product details. It does not differentiate from siblings such as search_products or get_product_images, which limits clarity in a crowded toolset.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus search_products or get_product_images. The only hint that it should follow a search comes from the product_id schema description, not the tool description itself.

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