Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kroger_products

Fetches full detail for up to 50 Kroger products in one bulk call, returning nutrition facts, allergens, store-scoped price and stock, rating histograms, and all image views.

Instructions

Get full Kroger product detail in bulk. Returns full detail for up to 50 Kroger products in one call. Carries materially more than kroger-product: a nutrition-facts panel with ingredients, allergens and dietary flags; store-specific price and stock level; a full star-rating histogram; the merchandising hierarchy; and every image perspective. location_id scopes price and stock to one store.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
upcsYesComma-separated Kroger product UPCs, up to 50
location_idNoKroger store/location id that scopes price and stock

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.2/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 full burden and does meaningful work: it discloses the returned payload (nutrition panel, allergens, dietary flags, price and stock, star histogram, merchandising hierarchy, image perspectives) and explains that location_id scopes price/stock. It omits any statement of read-only safety, rate limits, or behavior on invalid/unknown UPCs, which are the remaining gaps for a no-annotation tool.

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?

Four short sentences, front-loaded with the verb and scope, then the differentiator, then the parameter behavior. No filler or repetition; every sentence adds a distinct fact.

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?

With no output schema and only two parameters, the description must substitute for return documentation, and it does so by naming the major response sections. Minor omissions (safety/read-only signal, behavior for invalid UPCs, and whether results preserve input order) keep it short of fully complete.

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 description coverage is 100%, so both parameters are already documented in the schema, and the description largely restates them ('up to 50' matches the schema's comma-separated limit; the location_id sentence mirrors its schema description). It adds no new syntax, format, or edge-case guidance beyond the structured fields, so the baseline of 3 applies.

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 ('Get full Kroger product detail in bulk') and immediately distinguishes itself from the sibling kroger-product by enumerating the extra payload it carries. An agent can tell what this tool is and how it differs from other kroger_* tools without opening 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?

It clearly frames the use case (bulk lookup of up to 50 UPCs, richer detail than the single-item sibling), which implies when to choose it over kroger_product. However, it never explicitly states the selection rule (e.g. 'use this instead of kroger-product when you need more than one UPC or nutrition/price data') or when not to use it, leaving the agent to infer the boundary.

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