ah-mcp

Albert Heijn: Receipt Details

ah_get_receipt_details

Read-only

Retrieve full details for a single Albert Heijn in-store receipt by ID, including purchased items, quantities, prices, discounts, and payment method. Use an ID from the receipts list.

Instructions

Get full details of a single Albert Heijn in-store receipt (kassabon) by its id. Returns all purchased items with name, quantity, unit price and line total, plus any discounts and payment method. Get the id from ah_get_receipts first.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Receipt transaction ID from ah_get_receipts

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`items`	Yes
`payments`	No
`discounts`	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": {
+    "discounts": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "amount": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "amount"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "id": {
+      "type": "string"
+    },
+    "items": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "name": {
+            "type": "string"
+          },
+          "quantity": {
+            "type": "number"
+          },
+          "total": {
+            "type": "number"
+          },
+          "unit_price": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "name",
+          "total"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "payments": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "amount": {
+            "type": "number"
+          },
+          "method": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "method",
+          "amount"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "id",
+    "items"
+  ],
+  "type": "object"
+}

First observedv1.0.0Oct 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true, so safety is already covered, but the description adds substantive content: the returned payload (items with name, quantity, unit price, line total, discounts, payment method) and the prerequisite that the id must originate from ah_get_receipts. No mention of auth or error behavior for a missing/invalid id, which keeps it short of a 5.

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, zero filler: purpose, payload, and prerequisite in that order. The id-source instruction is front-loaded as the final actionable sentence where an agent will read it last before calling.

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?

For a single-parameter read tool with a full output schema and readOnly annotation, the description supplies everything needed: what it fetches, what comes back, and where the id comes from. Nothing required for correct invocation is missing.

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?

Schema description coverage is 100% and the single 'id' parameter is already documented as 'Receipt transaction ID from ah_get_receipts', which the description largely repeats. No added format, example, or validation semantics beyond the schema's own text.

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?

States a specific verb and resource ('Get full details of a single ... in-store receipt (kassabon) by its id'), scoped to the in-store receipt domain. This distinguishes it cleanly from ah_get_receipts (the list) and ah_get_order_details (orders, not kassabonnen).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicitly routes the agent: 'Get the id from ah_get_receipts first,' which establishes the required call ordering. It does not, however, state when to prefer ah_get_order_details for online orders versus this tool, leaving one sibling boundary to inference.

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