Skip to main content
Glama

Kroger

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is clear. Description adds context on scoping (by identifier) and the behavior of listing keys when argument omitted. Does not contradict annotations.

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?

Three sentences, front-loaded with core function. Every sentence adds value: main operation, when to use, scoping, and relationship to siblings. No wasted words.

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 simple retrieval tool with one optional parameter and strong annotations, the description covers main behavior, scoping, and sibling relationships. Could explicitly mention the return format (value or list of keys) but it is reasonably implied.

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?

Schema coverage is 100% with a description for the 'key' parameter. The description adds 'omit the key argument to list all keys' clarifying the optional behavior and the listing functionality, which is not explicit in the 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?

Description states 'Retrieve a value previously saved via remember, or list all saved keys' with specific verb+resource. Distinguishes from siblings remember and forget, and provides example use cases like user's target ticker or address. Clear scope and operation.

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 says when to use (look up context stored earlier), implies when not to use (save with remember, delete with forget), and mentions scoping by identifier. Provides explicit pairing with remember and forget, and gives examples of appropriate contexts.

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

All Kroger toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Many tools have overlapping purposes (e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, bet_research all query data), making it hard for an agent to choose the correct one. Additionally, entity_profile and compare_entities both provide company profiles, adding further ambiguity.

Naming Consistency2/5

Tool names are inconsistent: some use verb_noun (ask_pipeworx, compare_entities), some noun_verb (entity_profile), and some are single verbs (forget, recall). There is no clear pattern, and the mix of styles (e.g., kroger_*, polymarket_*, pipeworx_*) adds confusion.

Tool Count3/5

34 tools is on the higher end, but the server covers a broad domain (grocery, data query, betting, subscriptions). However, the presence of multiple similar query tools (e.g., three ask_pipeworx variants) inflates the count unnecessarily, making it feel bloated.

Completeness3/5

For its stated Kroger grocery focus, the tools (search, details, store locator) are complete. However, the server also includes many unrelated tools (betting, entity profiles, subscriptions) that feel tacked on, leaving gaps in coverage for the non-Kroger domains (e.g., no tools for user management or other store chains).

Resources