ah-mcp

Albert Heijn: Search Recipes

ah_search_recipes

Read-only

Search Albert Heijn's Allerhande recipes by Dutch keyword to get IDs, titles, URLs, cook times, servings, and nutrition scores; use IDs to view ingredients and steps.

Instructions

Search Allerhande, Albert Heijn's recipe collection. Dutch search terms work best, e.g. 'pasta', 'vegetarisch', 'stamppot', 'kip curry'. Returns id, title, url, cook_minutes, servings, courses, nutri_score, rating. Use the id with ah_get_recipe for ingredients and steps. When you mention a product or recipe from the result, link its name to its url.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results (default 10, max 30)
`query`	Yes	Search text, e.g. 'pasta zalm'

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`recipes`	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": {
+    "recipes": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "cook_minutes": {
+            "type": "number"
+          },
+          "courses": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "id": {
+            "type": "number"
+          },
+          "nutri_score": {
+            "type": "string"
+          },
+          "oven_minutes": {
+            "type": "number"
+          },
+          "rating": {
+            "type": "string"
+          },
+          "servings": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          },
+          "wait_minutes": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "recipes"
+  ],
+  "type": "object"
+}

First observedv1.0.0Oct 5, 2026

TDQS

A4.7/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 useful behavioral context beyond that: the search language preference, the id-to-detail workflow, and the result-linking convention. It does not cover rate limits or result ordering, 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, each earning its place, and it is front-loaded with what the tool searches before moving to query tips, return shape, and follow-up workflow. No filler.

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 return values need no explanation, yet the description still summarizes the key fields to aid selection. Combined with the ah_get_recipe routing and the linking instruction, an agent has everything needed to invoke and use this tool correctly.

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?

Schema description coverage is already 100%, so the baseline is 3. The description adds genuine semantic value for the query parameter by specifying that Dutch terms are preferred and giving domain-appropriate example terms, going beyond the schema's example. Limit is left to 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 (Search) and resource (Allerhande recipe collection), and names the concrete domain (Albert Heijn). This clearly separates it from the sibling ah_search_products, which searches products rather than recipes.

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?

Gives explicit usage guidance: Dutch search terms work best with concrete examples ('pasta', 'vegetarisch', 'stamppot', 'kip curry'), names the follow-up tool ah_get_recipe for ingredients and steps, and states the linking convention for results. The agent knows both how to query and what to do next.

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