Skip to main content
Glama
Kroger MCP Server

Kroger MCP Server

by CupOfOwls

check_chain_exists

Verify whether a grocery chain exists in the Kroger system by providing its name, so you can confirm valid chains before querying stores or products.

Instructions

Check if a chain exists in the Kroger system.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chain_name": "<chain_name>"
    },
    "name": "check_chain_exists"
  }
}

Input Schema

NameRequiredDescriptionDefault
chain_nameYesChain name, for example Kroger or Ralphs. See list_chains.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.4.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / chain_name / description
      Added value: +"Chain name, for example Kroger or Ralphs. See list_chains."
    • addedInput schema / properties / chain_name / minLength
      Added value: +1
    • removedInput schema / properties / chain_name / title
      Removed value: -"Chain Name"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior2/5

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

There are no annotations, so the description carries the full behavioral burden. It implies a read-only lookup through "Check," but does not explicitly state that it is non-mutating, whether authentication is required, or how invalid or missing chains are handled.

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?

The description is a single front-loaded sentence with no unnecessary wording. It conveys the tool's purpose immediately and wastes no space.

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 simple one-parameter existence check with a complete parameter schema and an output schema, the description is largely sufficient. Minor gaps remain around explicit read-only behavior and sibling-tool selection, but the core information needed to call the tool is present.

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%, and the chain_name parameter is already documented with an example and a pointer to list_chains. The description adds no additional meaning beyond what the schema provides, so the baseline of 3 applies.

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?

The description states a clear verb and resource: "Check if a chain exists" in the Kroger system. It does not explicitly differentiate this existence check from sibling tools like list_chains or get_chain_details, which keeps it from a 5.

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?

Usage is implied by the existence-check phrasing, but the description gives no explicit guidance on when to use this tool versus list_chains, get_chain_details, or check_location_exists. The agent must infer the appropriate context from the name and purpose alone.

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