Skip to main content
Glama
Kroger MCP Server

Kroger MCP Server

by CupOfOwls

test_authentication

Checks whether a Kroger user is signed in and the saved token is still valid, refreshing it when possible and returning authentication status.

Instructions

Check whether the user is signed in and the saved token has not expired.

An expired token is refreshed if possible. The check compares the token's expiry time with the clock, so a sign-in that Kroger revoked early still reports token_valid true until a cart call fails. A user who is not signed in is a normal result (token_valid false), not an error.

Returns: Dictionary indicating authentication status

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

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.2/5.0
Behavior4/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, and it does so well: it discloses the token-refresh side effect, the clock-comparison mechanism, and the important caveat that a revoked token still reports token_valid true until a cart call fails. What it lacks is any note on network or auth requirements or failure modes of the refresh itself.

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?

Front-loaded with the core purpose, then the refresh behavior, then the caveat, in a compact four-sentence body with zero waste. The trailing 'Returns:' block is slightly redundant against the output schema but does not bloat the description.

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?

An output schema exists, so the description need not explain return values, and the behavioral caveats it does provide are exactly what an agent needs to interpret the result correctly. Only the missing sibling routing keeps this from being fully complete for a no-parameter check tool.

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?

The tool takes zero parameters, so the baseline is a 4. Nothing in the description contradicts or muddies the empty schema.

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 check (whether the user is signed in and the saved token is not expired) with a clear predicate outcome. The scope is narrow enough that an agent can distinguish it from the sibling authentication tools such as get_authentication_info or force_reauthenticate without opening a schema.

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?

Implies usage context (verify sign-in state before an operation needing it) and helpfully notes that an unsigned-in user is a normal result, not an error. It never explicitly names an alternative or states when to prefer get_authentication_info or force_reauthenticate, leaving sibling routing to inference.

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