ask.recipes

List saved recipes

list_saved

Read-onlyIdempotent

List the recipes the user saved in ask.recipes, for "my recipes", "what did I save", "what's in my Stews cookbook". Each recipe lists the cookbooks it is in and the user's note; pass cookbook to see one cookbook only. Each also carries when it was last cooked and how many times, when mark_cooked recorded it. Not the Thermomix / Bimby / Cookidoo side; that is list_cookidoo_recipes.

Input Schema

Name	Required	Description	Default
`cookbook`	No	only recipes in this cookbook, by name; leave empty for every saved recipe, each listed with the cookbooks it is in

Output Schema

Name	Required	Description	Default
`recipes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

addedOutput schema / properties / recipes / items / properties / askrecipes_ratings
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / recipes / items / properties / my_rating

Added value: +{
+  "properties": {
+    "note": {
+      "type": "string"
+    },
+    "stars": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "stars"
+  ],
+  "type": [
+    "null",
+    "object"
+  ]
+}

Changed1 schema field changedOct 25, 2026
- addedOutput schema / properties / recipes / items / properties / main_protein
```
Added value: +{
+  "type": "string"
+}
```
Changed3 schema fields changedOct 25, 2026
- removedOutput schema / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / recipes / items / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / recipes / items / properties / cookbooks / items / additionalProperties
```
Removed value: -false
```
Changed1 schema field changedOct 24, 2026
- addedOutput schema / properties / recipes / items / properties / scale_class
```
Added value: +{
+  "type": "string"
+}
```
Changed2 schema fields changedOct 24, 2026
- addedOutput schema / properties / recipes / items / properties / last_cooked
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / recipes / items / properties / times_cooked
```
Added value: +{
+  "type": "integer"
+}
```

Changed3 schema fields changedOct 24, 2026

addedInput schema / properties

Added value: +{
+  "cookbook": {
+    "description": "only recipes in this cookbook, by name; leave empty for every saved recipe, each listed with the cookbooks it is in",
+    "type": "string"
+  }
+}

addedOutput schema / properties / recipes / items / properties / cookbooks

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "name": {
+        "type": "string"
+      },
+      "note": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

changedOutput schema / properties / recipes / items / required

Previous value: -[
-  "id",
-  "name",
-  "rating_count",
-  "source_site",
-  "source_url"
-]New value: +[
+  "id",
+  "name",
+  "rating_count",
+  "source_site",
+  "source_url",
+  "cookbooks"
+]

Changed1 schema field changedOct 19, 2026
- addedOutput schema / properties / recipes / items / properties / diets
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
```
Changed2 schema fields changedOct 18, 2026
- addedOutput schema / properties / recipes / items / properties / nutrition_for
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / recipes / items / properties / servings
```
Added value: +{
+  "type": [
+    "null",
+    "integer"
+  ]
+}
```
First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds useful context beyond that: each entry includes its cookbooks, the user's note, and last-cooked time/count as recorded by mark_cooked, which tells the agent what fields are meaningful and where they come from.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with purpose and immediately followed by the sibling exclusion. Slightly dense with quoted example phrases, but no sentence is 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?

A one-optional-parameter read tool with an output schema; the description covers purpose, triggering intents, filtering, sibling disambiguation and the provenance of the returned metadata. Nothing an agent needs to invoke it correctly 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 parameter already documents name-based cookbook filtering. The description restates the same behavior ("pass cookbook to see one cookbook only") without adding syntax, matching rules, or edge cases, so the schema does the heavy lifting — baseline 3.

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 the recipes the user saved") plus the owning surface (ask.recipes), and explicitly excludes the nearest sibling ("Not the Thermomix / Bimby / Cookidoo side; that is list_cookidoo_recipes"). An agent can distinguish it from list_cookidoo_recipes and list_cookbooks without opening any schema.

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 concrete user phrasings that trigger it ("my recipes", "what did I save", "what's in my Stews cookbook") and states the filtering condition for the one parameter. It also names the alternative tool to use for Cookidoo content, so both when-to-use and when-not-to-use are explicit.

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

All ask.recipes tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.