Skip to main content
Glama
Kroger MCP Server

Kroger MCP Server

by CupOfOwls

get_chain_details

Fetch detailed information for a specific Kroger grocery chain by chain name, helping users identify chain-specific store details.

Instructions

Get detailed information about a specific Kroger chain.

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

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

C2.9/5.0
Behavior2/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, yet it only implies read-only behavior through the verb 'Get'. It says nothing about what happens when the chain name is invalid or not found, or about any authentication/rate-limit characteristics.

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 zero filler. It is efficient, though its brevity borders on under-specification rather than optimal density.

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 simple one-parameter getter with an output schema and full schema coverage, the description is minimally sufficient. It leaves the not-found behavior and relationship to check_chain_exists unaddressed, which are the only meaningful gaps.

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 a single parameter with 100% schema description coverage, including an example ('Kroger or Ralphs') and a pointer to list_chains, so the schema already does the work. The description adds no additional meaning about name matching (exact vs fuzzy, case sensitivity).

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 chain'), which clearly separates it from list-style siblings such as list_chains. It does not explicitly name the sibling it contrasts with, but the singular 'specific chain' framing makes the distinction inferable.

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?

The description gives no when-to-use or when-not-to-use guidance. The only routing hint ('See list_chains') lives in the input schema's parameter description, not the tool description, and nothing explains the relationship to check_chain_exists or what to do when a chain is unknown.

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