Skip to main content
Glama
Kroger MCP Server

Kroger MCP Server

by CupOfOwls

get_location_details

Retrieve detailed information for a specific Kroger store location using its 8-character location ID.

Instructions

Get detailed information about a specific Kroger store location.

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": "get_location_details"
  }
}

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 carries the full burden. 'Get' weakly implies a non-destructive read, but it does not state authentication requirements, whether the call is rate-limited or cached, or what categories of detail are returned (the output schema covers return values, which lowers the bar somewhat). Adequate but thin.

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?

One short, front-loaded sentence with no wasted words. It is efficient, though it errs toward under-specification rather than excess.

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?

The output schema handles return values and the schema fully documents the single parameter, so the core is covered. However, with no annotations and a family of authentication siblings, the description should say whether this endpoint requires authentication or a preferred-location context; that gap keeps it at a minimum-viable 3.

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?

There is only one parameter and schema description coverage is 100%, including the 8-character format, an example value, and a pointer to search_locations. The description adds no meaning beyond the schema, so the 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?

States a specific verb (Get) and resource (detailed information about a specific Kroger store location), which is enough to distinguish it from search_locations by scope. It does not explicitly name the sibling it complements, so it stops short of 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 only implied: 'a specific store location' signals that a known identifier is required, and the schema tells the agent to obtain one from search_locations. The description itself never says when to call this versus search_locations or check_location_exists.

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