mcp-wikibooks-cookbook

Browse the Cookbook

list_recipes

Read-onlyIdempotent

Find recipes from the Wikibooks Cookbook by cuisine, dish type, or main ingredient. Narrow results by combining filters to discover dishes that match your cooking needs.

Instructions

Browse the Wikibooks Cookbook by cuisine, by kind of dish, or by main ingredient. Give at least one of the three; giving several narrows the result. This is built on the Cookbook's search, because the route this server is allowed to use publishes no way to list the members of a category. What comes back is therefore a ranked sample and not the category itself: it is neither complete nor ordered, and its length says nothing about how many recipes the Cookbook holds on the subject. The Cookbook also holds reference pages on ingredients and techniques, and those rank alongside recipes. Open a row with get_recipe before describing it as a recipe. Use search_recipes instead when there is a dish name to look up.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`cuisine`	No	A cuisine or a country, such as 'Italian' or 'Thai'.
`dish_type`	No	A kind of dish, such as 'soup', 'dessert' or 'bread'.
`main_ingredient`	No	The ingredient a recipe is built on, such as 'chicken' or 'lentils'.

Output Schema

TableJSON Schema

Name	Required	Description
`notes`	Yes
`query`	Yes	The search this server built from the arguments.
`source`	Yes
`cuisine`	Yes
`results`	Yes
`dish_type`	Yes
`result_count`	Yes
`main_ingredient`	Yes
`total_available`	Yes	Always null: no route reports how many recipes a category holds.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv2.1.0Sep 11, 2026
- removedOutput schema / properties / cuisine / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / cuisine / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / dish_type / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / dish_type / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / main_ingredient / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / main_ingredient / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / description / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / description / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / excerpt / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / excerpt / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / image_url / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / image_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```
Changed1 schema field changedv1.2.0Aug 7, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedv1.0.0Aug 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations declare readOnlyHint, openWorldHint, and idempotentHint, but the description goes far beyond those hints by explaining the underlying mechanism: it is built on the Cookbook's search because the allowed route cannot list category members. It explicitly warns that results are a ranked sample, not the full category, and that both recipes and reference pages appear. This extra context about incompleteness and ordering is exactly what an agent needs to avoid over-interpreting results.

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?

The description is concise yet dense with informationatrosphe: it states the purpose, gives usage guidance, discloses behavior, and names the sibling tool, all in a few sentences. It is front-loaded with the core purpose and scoping, and every sentence serves a clear function without redundancy. This is an efficient use of words.

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?

The tool has four parameters (all optional), an output schema exists, and the description covers the essential behavioral caveats and routing to sibling tools. Given the complexity of the tool (browsing vs search) and the presence of an output schema, the description is sufficiently complete. The agent has everything it needs to select and invoke the tool correctly: when to use, what to expect, and how to proceed.

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?

The schema already provides descriptions for each parameter (cuisine, dish_type, main_ingredient), and the description reinforces the semantics by explaining that at least one is required and that giving several narrows the result. The description adds the nuance about ranking but doesn't alter the basic meaning of each parameter. With a schema coverage of 75%, the baseline is 3, and the description adds slight value 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?

The description clearly states the tool's purpose: to browse the Cookbook by cuisine, dish type, or main ingredientchers. It specifies the resource (Wikibooks Cookbook) and the filtering dimensions, and it distinguishes itself from siblings by naming the alternative 'search_recipes' for dish name lookups. This is a specific verb+resource formulation that leaves no ambiguity.

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?

The description gives explicit when-to-use guidance: it says to use this tool for browsing by cuisine/dish/ingredient, and to use 'search_recipes' when there is a dish name to look up. It also advises opening rows with 'get_recipe' before describing something as a recipe, which clarifies the tool's role in a multi-step workflow. This level of situational guidance is exemplary.

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

Deploy Server