Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kroger_category

Browse a Kroger product category by slug and category ID to get paginated product cards, facet groups, and filters for sorting and refining results.

Instructions

Browse a Kroger category. Browses a Kroger product category and returns product cards plus facet groups, in the same shape as kroger-search. slug and category_id together identify the category (e.g. "pet" and "27" for kroger.com/pl/pet/27) -- call kroger-categories to discover every valid slug/category_id pair. It uses category_id as a taxonomy filter, with real pagination, and the source field reports which path answered. Facet filters and sort apply to the primary path only: when any of them is set, a failure of that path returns an error rather than silently falling back to unfiltered results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoOne-based result page
slugYesCategory URL slug segment. Obtain valid slug/category_id pairs from kroger-categories
sortNoResult order. One of: relevance, name_asc, popularity_desc
scentNoComma-separated scent facet values
brandsNoComma-separated brand names to filter by, taken verbatim from a previous response's facets
flavorNoComma-separated flavor facet values
savingsNoComma-separated savings facet values
nutritionNoComma-separated nutrition/dietary facet values
price_maxNoUpper bound of the price filter; required to filter on price
price_minNoLower bound of the price filter; defaults to 0
category_idYesCategory numeric taxonomy id. Obtain valid slug/category_id pairs from kroger-categories
more_optionsNoComma-separated more-options facet values

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • changedInput schema / properties / category_id / description
      Previous value: -"Category numeric taxonomy id"New value: +"Category numeric taxonomy id. Obtain valid slug/category_id pairs from kroger-categories"
    • changedInput schema / properties / slug / description
      Previous value: -"Category URL slug segment"New value: +"Category URL slug segment. Obtain valid slug/category_id pairs from kroger-categories"
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "name_asc",
+  "popularity_desc"
+]
  2. Addedv1.16.2

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it delivers meaningful behavior: real pagination, a 'source' field reporting which path answered, and the important asymmetry that facet filters and sort apply only to the primary path so path failure raises an error rather than silently returning unfiltered results. This is strong disclosure, though return-card structure and any auth/rate considerations remain unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, and every subsequent sentence adds operational detail. Slightly diminished by the near-redundant opening ('Browse a Kroger category. Browses a Kroger product category...'), but overall tight and well-ordered.

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?

For a 12-parameter, no-annotation, no-output-schema tool, this covers how the category is identified, what pagination looks like, how the source field behaves, and the filtered-request error semantics. The remaining gap (shape of returned product cards/facets) is partly covered by the reference to kroger-search.

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 baseline is 3, but the description adds real meaning: it explains that slug and category_id jointly identify the category (with a concrete example, 'pet'/'27'), that category_id acts as a taxonomy filter, and that facet filters are taken from prior facets. This goes beyond the schema text.

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 ('Browse a Kroger product category') and specifies what is returned ('product cards plus facet groups'), plus names the sibling whose shape it matches (kroger-search). An agent can distinguish it from kroger-categories and kroger-search without opening any 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?

Explicitly directs the agent to call kroger-categories to discover valid slug/category_id pairs, and explains the primary-path fallback semantics for filtered requests. Clear context, but it does not explicitly contrast when to browse a category versus using kroger-search, so it stops short of a full when/when-not/alternative statement.

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