Skip to main content
Glama
Kroger MCP Server

Kroger MCP Server

by CupOfOwls

check_location_exists

Validate an 8-character Kroger store location ID by confirming whether it exists in the Kroger system before using it for store-specific operations.

Instructions

Check if a location 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": {
      "location_id": "<location_id>"
    },
    "name": "check_location_exists"
  }
}

Input Schema

NameRequiredDescriptionDefault
location_idYes8-character store locationId, for example 01400513. Get one from search_locations.

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 / location_id / description
      Added value: +"8-character store locationId, for example 01400513. Get one from search_locations."
    • addedInput schema / properties / location_id / pattern
      Added value: +"^[A-Za-z0-9]{8}$"
    • removedInput schema / properties / location_id / title
      Removed value: -"Location Id"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure. 'Check' implies a read-only existence test, but the description does not explicitly state no side effects, permission needs, or rate limits; the output schema covers return values.

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?

It is a single front-loaded sentence with no redundant wording. It communicates the core operation efficiently.

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 low-complexity, one-parameter existence check with a fully described schema and an output schema, the description covers the essential purpose. The main missing piece is usage guidance versus alternatives, which prevents a 5.

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 coverage is 100% and the single location_id parameter is fully documented with pattern, example, and source in the schema. The description adds no parameter meaning beyond that, so baseline 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 specific verb ('Check') and resource ('location exists') in the Kroger system, making the operation clear. It does not explicitly contrast with nearby tools like search_locations or get_location_details, so sibling differentiation is left implicit.

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

Usage Guidelines2/5

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

No explicit when-to-use guidance or exclusions are given. The schema mentions getting an ID from search_locations, but the description does not say when this check is preferable to searching or fetching details.

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