ah-mcp

Albert Heijn: View Order Cart

ah_get_cart

Read-only

View the items, quantities, total price, and discount of the active Albert Heijn delivery order cart. Only after choosing a delivery or pick-up slot; before that, use the shopping list.

Instructions

View the items in the active Albert Heijn delivery order (the order cart). An order only exists after the user has chosen a delivery or pick-up slot; the products the user is collecting before that are on the shopping list (use ah_get_shopping_list). Returns the order state, items with names and quantities, total price, and total discount. When you mention a product or recipe from the result, link its name to its url.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`order`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.3.1Oct 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "order": {
+      "additionalProperties": false,
+      "properties": {
+        "id": {
+          "type": "number"
+        },
+        "items": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "name": {
+                "type": "string"
+              },
+              "price": {
+                "type": "number"
+              },
+              "product_id": {
+                "type": "number"
+              },
+              "quantity": {
+                "type": "number"
+              },
+              "url": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "product_id",
+              "url",
+              "quantity"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "state": {
+          "type": "string"
+        },
+        "total_discount": {
+          "type": "number"
+        },
+        "total_price": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "id",
+        "items"
+      ],
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedv1.0.0Oct 5, 2026

TDQS

A4.6/5.0

Behavior4/5

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

readOnlyHint already covers safety, and the description adds real behavioral content: the payload contains order state, item names/quantities, total price and total discount, plus an instruction to hyperlink product/recipe names to their urls. It doesn't cover edge cases such as an empty or expired cart, but against annotation coverage this is solid.

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 sentences, front-loaded with the core action and scoped with the sibling alternative. The return-value enumeration and the url-linking instruction are marginally beyond what this tool needs, but nothing is wasted or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Zero parameters plus an existing output schema means the remaining burden is selection and expectation-setting, and the description covers both: when a cart exists, what it contains, and how to reference items in the reply. Nothing an agent needs to call it correctly is missing.

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?

There are zero parameters, so the schema has nothing for the description to annotate; the baseline for a no-arg tool is 4. The description correctly adds no invented parameter semantics.

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?

Specific verb+resource ('View the items in the active Albert Heijn delivery order') with the scope clarified as the order cart after slot selection. It explicitly distinguishes itself from the shopping list, which is the most likely sibling to confuse it with, so an agent can select correctly 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the precondition for an order existing (a delivery or pick-up slot must be chosen) and names the alternative tool (ah_get_shopping_list) for the pre-slot period. This is explicit when-to-use/when-to-use-else guidance rather than inference.

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