ask.recipes

What the user cooked

cooked_history

Read-onlyIdempotent

List what the user cooked and when, newest first, for "what did we cook last week", "when did I last make the lasagna", "what have we been eating". Call it before planning a week so the plan avoids repeating recent dishes and ingredients. Each entry carries the day, the user's note and the recipe summary with its source link. Without since, until or recipe_id it covers the last 30 days.

Input Schema

Name	Required	Description
`limit`	No	max entries, default 50, max 200
`since`	No	first day to include as YYYY-MM-DD; without since, until or recipe_id the last 30 days are returned
`until`	No	last day to include as YYYY-MM-DD, inclusive
`recipe_id`	No	only entries for this recipe, for 'when did I last make the lasagna'; lifts the 30-day default

Output Schema

Name	Required	Description	Default
`entries`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026
- addedOutput schema / properties / entries / items / properties / cooked_by
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedOct 29, 2026

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

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

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: newest-first ordering, the default 30-day window and what lifts it, and the shape of each entry (day, note, recipe summary with source link).

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?

Purpose and ordering are front-loaded, the example utterances are tightly grouped, and the workflow hint follows. The closing sentence on the 30-day default duplicates the schema text, a small redundancy that keeps it out of the top band.

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?

With full schema coverage, rich annotations and an output schema, everything an agent needs is present: what it returns, default scope, ordering, and when to invoke it. No meaningful gap remains.

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 four parameters are already documented. The description's statements about the 30-day default and recipe_id lifting it restate the schema rather than adding new semantics, so the 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 (list cooked history) plus ordering ('newest first'), and the example utterances ('when did I last make the lasagna') make the retrieval shape unambiguous against siblings like mark_cooked or get_recipe.

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?

Explicitly says to call it before planning a week so plans avoid repeating dishes and ingredients, which gives a clear triggering context. It stops short of naming an alternative tool or stating when-not to use it, so it falls just under the top band.

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.