Skip to main content
Glama
Kroger MCP Server

Kroger MCP Server

by CupOfOwls

force_reauthenticate

Clear the saved authentication token to force re-authentication, fix login issues, or switch users while preserving local cart and order history.

Instructions

Force re-authentication by clearing the current authentication token. Use this if you're having authentication issues or need to log in as a different user.

This deletes the saved user token. The local cart tracking and order history are kept.

Returns: Dictionary indicating the re-authentication was initiated

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "force_reauthenticate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the destructive side effect ('deletes the saved user token') plus what survives ('local cart tracking and order history are kept'). It stops short of saying the session is immediately invalidated or that re-login is mandatory afterward, but the core blast radius is clear.

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?

Front-loaded with the action and its mechanism, then triggers, then the data-preservation note. The trailing 'Returns:' block is redundant given a real output schema exists, costing a small amount of space but not obscuring anything.

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 zero-parameter mutation with no annotations, it covers the action, the trigger, and the side effects on persisted data. The only missing piece is what happens to the current session immediately after clearing — whether the agent must call start_authentication next.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so there is nothing to disambiguate; the baseline of 4 applies. The description correctly implies this is a no-argument, unconditional operation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and mechanism ('Force re-authentication by clearing the current authentication token'), which unambiguously separates it from siblings like test_authentication, start_authentication, and complete_authentication. An agent can tell this is a reset/cleanup action rather than part of the login flow.

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

Usage Guidelines5/5

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

Explicitly names both trigger conditions: authentication problems, or switching to a different user. That is precisely the when-to-use guidance that distinguishes it from the sibling authentication tools, with no inference required.

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