Kroger MCP Server

Overview Schema Source Related Servers Discussions Admin

view_order_history

Retrieve recently placed orders recorded through this MCP server and review their history; results are limited to 1-50 orders explicitly marked as placed here, not Kroger's full order history.

Instructions

View the history of placed orders.

Note: This tool can only see orders that were explicitly marked as placed via this MCP server. The Kroger API does not provide permission to query the actual order history from Kroger's systems.

Input Schema

Name	Required	Description	Default
`limit`	No	Number of recent orders to show (1-50)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.4.0Oct 27, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / limit / description
```
Added value: +"Number of recent orders to show (1-50)"
```
- addedInput schema / properties / limit / maximum
```
Added value: +50
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedAug 15, 2025

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the single most important behavioral trait: the data source is local state, not Kroger's systems, due to API permission limits. It does not explicitly state read-only semantics or ordering/pagination behavior, but the critical limitation is front and center.

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?

Two short sentences, both earning their place, with the core purpose stated first and the caveat immediately after. No filler or repetition of the name.

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 one-optional-param read tool with an output schema, the description covers purpose, data scope, and the reason for that scope — enough to call it correctly. Minor gap: it doesn't say what an empty result implies beyond the caveat or how results are ordered.

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

Parameters3/5

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

One optional parameter with 100% schema coverage, where the schema already documents range 1-50 and the default. The description adds no syntax or semantics beyond what the schema provides, so the baseline of 3 applies.

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?

Specific verb+resource ("View the history of placed orders") with an added scope qualifier that separates it from Kroger's real order history. It does not explicitly name a sibling like mark_order_placed or view_current_cart as the counterpart, so sibling differentiation is only implied.

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 note tells the agent this only returns orders flagged via this MCP server, which is useful context for interpreting empty results, but it never states when to call this versus view_current_cart or that mark_order_placed must precede it. Usage is inferable rather than stated.

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