Skip to main content
Glama
Kroger MCP Server

Kroger MCP Server

by CupOfOwls

list_chains

Retrieve all Kroger-owned grocery chains to identify available brands and chain details for store or product queries.

Instructions

Get a list of all Kroger-owned chains.

Returns: Dictionary containing chain information

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_chains"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.5/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 disclosure burden. It does state the return shape ('Dictionary containing chain information'), but says nothing about read-only semantics, required authentication, result size, or pagination — all plausible concerns for a live grocery API.

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?

Two short lines with the action stated first and no filler. The 'Returns' line is largely redundant given an output schema exists, which is the only minor inefficiency.

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?

For a zero-parameter list tool with an output schema, the return values do not need explaining, and the description is nearly sufficient. It falls short on operational context — auth requirements, whether the list is exhaustive or paginated, and how it relates to the chain lookup siblings.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter semantics for the description to elaborate. The schema's empty object with additionalProperties: false already makes the no-argument contract unambiguous.

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 specific verb and resource (get/list all Kroger-owned chains) with a scope qualifier ('all') that implicitly separates it from single-chain siblings like get_chain_details and check_chain_exists. It never names those alternatives explicitly, so the differentiation is left to inference.

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

Usage Guidelines3/5

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

The word 'all' hints that this is the enumeration tool rather than a lookup, which is useful implied guidance. But there is no explicit when-to-use statement, no mention of when to prefer get_chain_details or check_chain_exists, and no note about authentication prerequisites despite an auth flow existing in the sibling set.

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