Skip to main content
Glama
CupOfOwls

Kroger MCP Server

by CupOfOwls
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_product_images

Retrieve a product image from a specified perspective; check product details first to see available views such as front, back, left, or right.

Instructions

Get an image for a specific product from the requested perspective.

Use get_product_details first to see what perspectives are available (typically "front", "back", "left", "right").

Input Schema

NameRequiredDescriptionDefault
product_idYes13-digit productId or UPC, for example 0001111041700. Get one from search_products.
location_idNo8-character store locationId, for example 01400513. Defaults to the preferred location set with set_preferred_location.
perspectiveNoThe image perspective to retrieve (default: "front")front

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.4.0
    • 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 / perspective / description
      Added value: +"The image perspective to retrieve (default: \"front\")"
    • addedInput schema / properties / perspective / minLength
      Added value: +1
    • removedInput schema / properties / perspective / title
      Removed value: -"Perspective"
    • 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"
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that available perspectives vary per product (typically front/back/left/right), which prevents blind guesses, but it never says what is returned (image URL vs. binary data), whether the call is read-only, or how failures surface.

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?

Two sentences, zero waste, with the core action stated first and the prerequisite second. Every sentence earns its place and nothing is buried.

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?

With no output schema, the agent must infer the return type (image payload vs. URL) from the name alone, which is a meaningful gap for an image-fetching tool. The prerequisite and perspective hints are good, but the 'what comes back' question is left unanswered.

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?

Schema coverage is 100%, so the baseline is 3, and the description adds genuine value by naming the typical perspective values ('front', 'back', 'left', 'right') that the schema leaves open as a free-form string with no enum. It adds nothing about product_id or location_id, which the schema already documents thoroughly.

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 ('Get an image for a specific product') plus a qualifier ('from the requested perspective'), and explicitly points at get_product_details as the companion tool, so the agent can separate it from the product-detail sibling without reading either schema.

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?

Gives a clear sequencing rule: call get_product_details first to discover which perspectives exist, rather than guessing. It stops short of stating what to do when the requested perspective is unavailable or when not to call this tool, so it is clear but not exhaustive.

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

Deploy Server

Other Tools