Skip to main content
Glama
Kroger MCP Server

Kroger MCP Server

by CupOfOwls

get_user_profile

Retrieves profile data for the signed-in Kroger user, enabling assistants to access account information for personalized grocery interactions.

Instructions

Get the authenticated user's Kroger profile information.

The Identity API needs a sign-in that grants the profile.compact scope.

Returns: Dictionary containing user profile data

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_user_profile"
  }
}

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.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the auth prerequisite ('needs a sign-in that grants the profile.compact scope'), which is real behavioral context an agent needs. However, it omits what happens on missing/invalid sign-in (error vs empty result) and whether the call has side effects.

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?

Three short lines, front-loaded with the action and a real prerequisite. The 'Returns: Dictionary containing user profile data' line is largely redundant given an output schema exists, which slightly dilutes an otherwise tight 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?

A zero-parameter read with an output schema needs little more than the auth prerequisite, which is supplied. The only missing element is failure behavior when the scope requirement is unmet.

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 4. Nothing is left ambiguous about inputs, and the description correctly signals the target is implicitly the authenticated user rather than a passed ID.

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 and resource: 'Get the authenticated user's Kroger profile information.' An agent can distinguish it from get_user_zip_code and get_authentication_info by the 'profile information' framing, though the description never names those siblings explicitly.

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?

Usage is implied rather than stated: the tool retrieves the current (authenticated) user's profile, and the scope prerequisite is a strong hint about context. But there is no explicit when-to-use, when-not-to-use, or routing to an alternative sibling.

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