Skip to main content
Glama
Kroger MCP Server

Kroger MCP Server

by CupOfOwls

set_preferred_location

Sets the preferred store location for future operations using an 8-character location ID from search_locations.

Instructions

Set a preferred store location for future operations.

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

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.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden for a mutation tool. It signals persistence ('future operations') but says nothing about whether an existing preference is overwritten, whether the change is reversible, whether authentication is required, or what happens if the location id is invalid.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity is part of why behavioral coverage is thin.

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 tool is simple (one required parameter), an output schema exists so return values need not be described, and the schema fully documents the parameter. The remaining gap is behavioral: a persistent-state mutation with zero annotations and no description of overwrite/reversibility or side effects on later operations.

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 location_id description already specifies the 8-character format, a concrete example, and how to obtain a value via search_locations. The description adds nothing beyond that, 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 names a specific verb ('Set') and resource ('preferred store location'), and the phrase 'for future operations' hints at the persistence semantics that distinguish it from get_preferred_location. It does not explicitly name the read-side sibling, so the differentiation is implicit rather than stated.

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?

'For future operations' implies this is a persistent setting that affects subsequent calls, which is a weak form of usage context. There is no explicit statement of when to prefer this over get_preferred_location or what prerequisite (a valid location from search_locations) is needed; that prerequisite appears only in the schema, not the description.

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