ah-mcp

Albert Heijn: Order Details

ah_get_order_details

Read-only

Retrieve the full item list for a specific Albert Heijn delivery order by ID, returning each product's name, quantity, and price.

Instructions

Get the full item list for a specific Albert Heijn delivery order by its ID. Returns all products with names, quantities, and prices. Get order_id from ah_get_orders. When you mention a product or recipe from the result, link its name to its url.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`order_id`	Yes	Numeric order ID from ah_get_orders

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`items`	Yes
`state`	No
`total_price`	No
`total_discount`	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": {
+    "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"
+}

First observedv1.0.0Oct 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds value beyond that by disclosing the return contents (products with names, quantities, prices) and an output-handling convention: link product/recipe names to their url when mentioned. It stops short of noting empty orders or failure modes.

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 short sentences, each earning its place: what it does, what it returns, how to source the ID, and how to render the result. The core purpose is front-loaded and there is no filler.

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?

An output schema exists, so return-value structure need not be explained, and readOnlyHint covers safety. The description supplies the remaining context an agent needs: parameter provenance and the linking convention. Minor gaps (empty/nonexistent order handling) keep it from a 5.

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 order_id parameter is already documented as 'Numeric order ID from ah_get_orders'. The description's provenance note largely restates the schema, so per the baseline rule a 3 is appropriate even though it is not misleading.

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 the full item list for a specific Albert Heijn delivery order by its ID') and immediately clarifies the granularity, distinguishing it from the sibling ah_get_orders which lists orders rather than their line items. An agent can tell them apart without opening either schema.

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?

Gives an explicit prerequisite chain: 'Get order_id from ah_get_orders', which tells the agent this tool must be preceded by the list tool and how to obtain the required parameter. It does not state any when-not conditions or error behavior, but the routing context is clear.

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