ask.recipes

Create a cookbook

create_cookbook

Create an empty cookbook, for "make me a BBQ cookbook". Not needed before save_recipe, which creates a cookbook it does not know. Fails when a cookbook with that name exists already. shared=true makes it a household cookbook, visible to everyone in the user's household.

Input Schema

Name	Required	Description
`name`	Yes	cookbook name, e.g. 'BBQ', 'Weeknight', 'Christmas'
`shared`	No	true to make it a household cookbook that everyone in the user's household sees and saves into, for 'a cookbook for the whole family'; needs a household
`description`	No	one line on what goes in it

Output Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`shared`	No
`default`	No
`description`	No
`recipe_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 31, 2026

addedInput schema / properties / shared

Added value: +{
+  "description": "true to make it a household cookbook that everyone in the user's household sees and saves into, for 'a cookbook for the whole family'; needs a household",
+  "type": "boolean"
+}

addedOutput schema / properties / shared
```
Added value: +{
+  "type": "boolean"
+}
```

Changed1 schema field changedOct 25, 2026
- removedOutput schema / additionalProperties
```
Removed value: -false
```
AddedOct 24, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, non-idempotent, closed-world, so safety is covered. The description adds value beyond that with the duplicate-name failure mode and the cross-user visibility consequence of shared=true, which no annotation expresses. It stops short of describing the return value, but an output schema exists.

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 short sentences, each doing distinct work: create, sibling routing, and shared semantics. The opening quoted example is slightly awkward, but nothing is padded or buried.

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?

With annotations covering mutability and an output schema covering returns, the remaining burden is when-to-use and edge cases—both addressed (duplicate name, save_recipe overlap, household prerequisite). Minor omission: no statement about what permissions or scope the new cookbook lands in beyond shared.

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 all three parameters are already documented—including the household requirement for shared and example names. The description's shared=true sentence mostly restates the schema's own wording, adding only the household-scoping phrasing; baseline 3 applies.

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 ('Create an empty cookbook') and immediately anchors it to a real-world intent ('make me a BBQ cookbook'). Crucially, it distinguishes itself from save_recipe, the sibling that also creates cookbooks, so an agent can tell the two apart without opening schemas.

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?

Explicitly says when this tool is NOT needed ('Not needed before save_recipe, which creates a cookbook it does not know'), which is exactly the routing decision an agent would otherwise get wrong. It also names the failure condition (duplicate name), giving a clear precondition.

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.