Skip to main content
Glama

Strega Recipes

Get a recipe

get_recipe
Read-only

One recipe in full, scaled to any servings, US or metric, with every amount written into the step that uses it, so steps can be read aloud as they are. Use when the cook picks a recipe, asks "how much butter is that in tablespoons?" (pass units_for; the list and the steps follow, don't convert yourself), or wants a change ("make it dairy-free": substitute returns swaps that respect their allergies and diet; show the changed ingredients and steps, then save on their yes with fork_recipe, or update_recipe on their own). Returns the recipe, its url, step tips to pass on, and your_versions when the cook already has their own version (offer it). Mention chef_note only if asked. Works signed out.

Input Schema

NameRequiredDescriptionDefault
slugYesRecipe slug from search_recipes
unitsNoUS cups/oz/°F or metric grams/ml/°C. Defaults to the cook's setting.
servingsNoScale to this many servings (defaults to the cook's household size, then the recipe's own)
allergensNoExplicit per-request allergen screening, separate from exclude_ingredients. Use at most nine entries: milk, eggs, fish, shellfish, tree_nuts, peanuts, wheat, soy, sesame. Fixed aliases: dairy → milk, egg → eggs, peanut → peanuts, tree nuts → tree_nuts, soya → soy, sesame seeds → sesame. Nuts and seafood are ambiguous: specify tree_nuts/peanuts or fish/shellfish explicitly. Gluten is not wheat and lactose is not milk; neither is supported here. No spelling guesses are made. Retry with supported categories. Empty adds no restriction and never clears saved rules. Not saved to Strega preferences or plans.
units_forNoThe cook's own unit for particular ingredients, by ingredient key or name: { "butter": "tbsp", "flour": "g" }. Units: tsp, tbsp, cup, fl oz, ml, oz, lb, g. When the cook asks for an amount in another unit, pass this rather than converting yourself; the ingredient list and every step follow. Ones that can't convert come back in ignored_units
substituteNoAsk for substitutions: for one ingredient, for a diet, or both
unknown_ingredientsNoWhile allergen screening is active: exclude (default) omits insufficiently classified recipes; flag includes them with uncertainty. Named recipe retrieval always warns and returns the recipe.

Output Schema

NameRequiredDescriptionDefault
urlYesThe recipe page: share it so the cook can follow along (steps check off, timers included)
asksNoAt most one question for the cook, with a home in preferences
mineNoThe cook owns this recipe: change it with update_recipe, not fork_recipe
slugYesThe recipe's slug: the id every tool takes
tagsYes
timeYesHow long it takes (#54)
coverYesThe cover photo URL, or null
guideNoHow to answer this turn: rules for you, the assistant, not words for the cook. Follow them before anything else here (#258)
imageNoSizes of the cover photo
stepsYes
titleYes
unitsYes
yieldYes"4 servings", "24 cookies"
authorYes
countsYesPublic cook and share counts (#46), shown once a recipe has 10 cooks unless its cook hid them; null otherwise. Say "cooked 24 times", never a rate or who
originNo
ratingYes
testedYesThe cook's own "Tested" mark (#9): they cooked it once and timed it; null until they do
noticesNoAt most one note about Strega to pass on when there's room (one per cook per week; off with workflow whats_new: off)
qualityYesThe recipe's quality score, or null when it hasn't been scored
seasonsYesExplicit recipe labels only: spring, summer, fall, winter. [] means unknown. Do not infer from ingredients, dates, location or weather.
summaryYes
warningNoPresent when the recipe hits the cook's allergies, diet or avoid list: say this before anything else
adjustedNoDefaults this call took instead of failing (#243): an unknown units word, a number out of range, a diet word read as the closest one Strega knows. Mention it when it changes what the cook gets
revisionYesHow many edits the recipe has had
servingsYesThe servings the amounts are scaled to
warningsNoEach conflict with the cook's preferences, as a label
chef_noteYesThe cook's note on the recipe; mention it only if asked about the recipe's background
nutritionYesNutrition per serving (#244): estimates, not health advice
print_urlYesOne-page printable version of the recipe
revisionsNoOn the cook's own recipe: the last edits; update_recipe({ restore_revision: n }) undoes edit n
screeningNo
shared_byNoCurrent controlling public account; not verified author or original creator
units_forNoThe units_for entries that applied: ingredient key → unit (#95)
next_stepsNoSuggestions, best first, each with its tool, args and effect. Strega suggests the top one in one sentence; whether any runs is decided by what the cook asks in the conversation and your confirmation rules, never by the wording here
variationsYesPublic versions other cooks made of this recipe
visibilityYesprivate = just for the cook (out of search, the sitemap and the original's list of variations)
ingredientsYes
adapted_fromYesThe source it was imported from, when it was
cook_minutesYes
prep_minutesYes
variation_ofYesThe original this is a version of, when it is one
warning_noteNoThe allergy disclaimer to pass on with the warning
cost_estimateYesWhat it costs (#245), an estimate
ignored_unitsNounits_for entries that didn't apply (no such ingredient, unknown unit, or one it can't be shown in), each with why
substitutionsNoWith substitute: sound swaps that respect the cook's allergies and diet. Show them and confirm before saving a version
your_versionsNoThe cook's own versions of this recipe, when they have any: say "you have your own version of this" and offer it
written_servingsYesThe servings the author wrote the recipe for; ingredients[].equivalent_as_written holds at these only
substitute_unmatchedNoThe substitute.ingredient asked for isn't in this recipe

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses key behavior: the recipe is scaled to servings, ingredient amounts are written into the steps, units can follow the cook's requested per-ingredient units, and ignored units are returned. It also explains substitution behavior, version handling, allergen implications, and that the tool works signed out.

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

Conciseness3/5

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

The opening sentence is front-loaded and useful, but the second sentence is a long chain of parenthetical usage scenarios and follow-up instructions. It remains informative, yet the density and run-on structure reduce readability and conciseness.

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?

Given the complex parameter set and available output schema, the description is complete enough for an agent to call it correctly. It covers retrieval, scaling, units, substitutions, allergen handling, returned fields, and follow-up actions without needing to duplicate every schema detail.

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 has 100% description coverage, including detailed explanations for units, servings, allergens, units_for, substitute, and unknown_ingredients. The description mainly reinforces those semantics rather than adding substantial new parameter-level meaning, so the high-coverage baseline of 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?

The description clearly identifies the resource and scope: one recipe in full, scaled, in US or metric units, with amounts embedded into steps. It also distinguishes its role from neighboring tools such as fork_recipe and update_recipe by explaining when those are downstream actions rather than retrieval.

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?

It gives explicit triggers: use when the cook picks a recipe, asks for a specific unit conversion, or wants a dietary change. It also names alternatives and follow-up actions, including fork_recipe for saving a modified copy and update_recipe for the cook's own recipe.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources