ask.recipes

Import a Cookidoo recipe

import_cookidoo_recipe

DestructiveIdempotent

Copy one Cookidoo recipe into the user's private ask.recipes collection, so the agent can read it in full, adapt it, build a shopping list, or compare it with other recipes. Imported recipes are visible only to this user and cannot be shared. Importing the same recipe again refreshes the copy.

Input Schema

Name	Required	Description	Default
`cookidoo_id`	Yes	Cookidoo recipe id such as r123456 or a created-recipe id, from search_cookidoo, list_cookidoo_recipes or the recipe's Cookidoo URL

Output Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`diets`	No
`fat_g`	No
`units`	No
`yield`	No
`rating`	No
`carbs_g`	No
`fiber_g`	No
`sugar_g`	No
`calories`	No
`saved_in`	No
`servings`	No
`image_url`	No
`my_rating`	No
`nutrition`	No
`protein_g`	No
`scale_note`	No
`source_url`	Yes
`attribution`	Yes
`description`	No
`ingredients`	Yes
`scale_class`	No
`source_site`	Yes
`cook_minutes`	No
`instructions`	Yes
`main_protein`	No
`prep_minutes`	No
`rating_count`	Yes
`nutrition_for`	No
`total_minutes`	No
`askrecipes_ratings`	No
`scaled_from_servings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

addedOutput schema / properties / saved_in

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

Changed1 schema field changedOct 30, 2026
- addedOutput schema / properties / units
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedOct 29, 2026

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

addedOutput schema / 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 / main_protein
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedOct 25, 2026
- addedOutput schema / properties / scale_note
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedOct 25, 2026
- removedOutput schema / additionalProperties
```
Removed value: -false
```
Changed1 schema field changedOct 24, 2026
- addedOutput schema / properties / scale_class
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / cookidoo_id / description

Previous value: -"Cookidoo recipe id such as r123456, from search_cookidoo or the recipe's Cookidoo URL"New value: +"Cookidoo recipe id such as r123456 or a created-recipe id, from search_cookidoo, list_cookidoo_recipes or the recipe's Cookidoo URL"

AddedOct 20, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=true; the description explains both by disclosing that re-importing the same recipe refreshes the copy, and adds the privacy constraint that imported recipes are visible only to this user and cannot be shared. It does not mention the prerequisite Cookidoo account link, which is the main operational unknown left.

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, front-loaded with the verb and destination, then use cases, then the two behavioral caveats (privacy, refresh semantics). Nothing is repeated from the schema or annotations.

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-shape explanation is unnecessary, and the annotations carry the safety profile while the description reinforces it. The remaining gap is the unstated dependency on connect_cookidoo before importing can succeed.

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 coverage is 100% for the single required parameter, and the schema itself already documents accepted id formats (r123456, created-recipe ids, URL). The description adds no further meaning about cookidoo_id, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Copy one Cookidoo recipe into the user's private ask.recipes collection') plus the target scope, which separates it from the plural sibling import_recipes and from save_recipe. It never names the alternative import tool explicitly, so differentiation is implied by 'one' rather than stated.

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 concrete downstream uses ('read it in full, adapt it, build a shopping list, or compare it with other recipes') that tell an agent when this import is worthwhile. It stops short of explicit exclusions — e.g. when to prefer import_recipes or save_recipe, or that a Cookidoo connection must exist first.

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.