ah-mcp

Albert Heijn: Orders

ah_get_orders

Read-only

List Albert Heijn online delivery orders: upcoming by default, or delivered orders with past=true. Returns order ID, date, time, total, and status for viewing details.

Instructions

List Albert Heijn online delivery orders. By default returns upcoming orders (with a modifiable flag); set past=true for delivered orders. Returns id, date, time_window, total_price, status. Use the returned id with ah_get_order_details to see the items.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`past`	No	Return delivered orders instead of upcoming ones
`limit`	No	Maximum number of orders to return (default 10)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`orders`	Yes

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": {
+    "orders": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "id": {
+            "type": "number"
+          },
+          "modifiable": {
+            "type": "boolean"
+          },
+          "shopping_type": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          },
+          "time_window": {
+            "type": "string"
+          },
+          "total_price": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "orders"
+  ],
+  "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?

readOnlyHint=true is already supplied, so safety is covered. The description adds meaningful behavior: the default result set is upcoming orders, past=true flips it, and the response shape (id, date, time_window, total_price, status) is disclosed. The phrase 'with a modifiable flag' is vague, but the semantics of the flag are clarified by the schema.

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 compact sentences, front-loaded with purpose and default behavior, then the flag, then the hand-off to the detail tool. No filler or repetition.

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?

An output schema exists, so enumerating return fields in prose is optional, but everything an agent needs to invoke the tool correctly is present: default scope, the past flag, and the next-step routing. No gaps remain for a two-optional-parameter list tool.

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%, so both parameters are documented structurally; baseline is 3. The description reinforces the meaning of past by contrasting upcoming vs delivered orders and notes the default upcoming scope, but adds no format, units, or edge-case detail beyond 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?

States a specific verb and resource ('List Albert Heijn online delivery orders') and immediately scopes it to two modes (upcoming by default, delivered with past=true). An agent can distinguish this from ah_get_order_details, which is explicitly named as the drill-down sibling.

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 clear context: default is upcoming orders, and past=true switches to delivered orders. It also routes the agent forward ('Use the returned id with ah_get_order_details'), which is exactly the follow-up guidance an agent needs. It stops short of stating when *not* to use this tool or when to prefer another listing alternative.

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