Skip to main content
Glama
Kroger MCP Server

Kroger MCP Server

by CupOfOwls

get_authentication_info

Retrieves the current Kroger authentication state and token details, so you can check whether a user is signed in before making account-specific requests.

Instructions

Get information about the current authentication state and token.

A user who is not signed in is a normal result (authenticated false), not an error.

Returns: Dictionary containing authentication information

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

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

A3.9/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. It usefully discloses that authenticated=false is a normal result rather than an error and that the tool returns authentication information including a token; it does not elaborate on permissions, token sensitivity, or side effects, but for a zero-parameter read tool this is reasonably transparent.

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?

The description is short and front-loaded: it states the purpose first, then highlights the key non-error behavior, then notes the return shape. Every sentence adds useful information without repetition.

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?

Given the low complexity, zero parameters, and existing output schema, the description is nearly complete. It covers the main purpose and the important unauthenticated case, though it could more explicitly relate the tool to sibling authentication operations.

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 has zero parameters and 100% schema coverage, so parameter semantics are not a concern. The description appropriately adds no parameter detail because none is needed.

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 uses a specific verb and resource: get current authentication state and token. It is clear enough to distinguish from most siblings, but it does not explicitly differentiate itself from nearby authentication tools such as test_authentication or force_reauthenticate.

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?

The description implies usage by stating that an unauthenticated result is normal, which helps an agent interpret the call. However, it does not explicitly say when to use this tool versus test_authentication, start_authentication, or complete_authentication.

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