What to cook: how to refine queries and get practical recipes
The "What to cook" tool helps turn a list of available products into specific recipes. There are four fields in the form: ingredients and quantities, preferences and restrictions, people or portions, available time. Based on this data, the service generates one result, which can be copied or downloaded as a plain text file. The first option is often general, so it is useful to refine it. In this guide we will go through how to fill in the fields sequentially, analyze the suggestions and adapt them to your conditions. We will not invent nonexistent functions — only those capabilities that exist in the interface. You will learn to use these fields for iterative recipe improvement and get practical skills working with the tool.
Open tool: Recipe generator ↗Why the first result requires refinement
The first generated recipe is often too general: the model offers a basic product combination but does not account for your actual quantities, taste preferences or exact time. For example, if you specified "potatoes, carrots, onions, lentils and tomatoes" and "dinner for two in 30 minutes", the tool may suggest a stew, but without indicating proportions and cooking steps. Such a result is useful as a starting point, but it needs refinement.
Refinement starts with analyzing what exactly did not suit you: missing specific grams, too vague steps, a dish that does not match a dietary restriction or preparation time exceeding the available time. The more specifically you describe the problem, the more precise the next request will be. Do not hesitate to return to the form and change the wording — this is the main way to improve the result.
First query: "potatoes, carrots, onions, lentils, tomatoes; dinner for two in 30 minutes". First result: "Vegetable stew with lentils". Problem: not indicated how much of what to take and how to achieve a rich taste in 30 minutes.
Refining ingredients and quantities
In the "Ingredients and quantities" field it is important to indicate not only names but approximate volumes: "2 medium potatoes, 1 carrot, 1 onion, 200 g cooked lentils, 3 tomatoes". If exact quantities are not available, indicate at least proportions: "roughly equal amounts of potato and carrot". This helps the tool suggest realistic proportions and avoid taste imbalance.
If after the first result you realize some products are missing or unnecessary, adjust the list. For example, add "1 tbsp tomato paste" for richness or omit lentils if they do not combine with the rest. You can also indicate the desired texture: "I want a thick stew, not a soup". The tool does not have a separate texture field, but it can be described in restrictions or in a comment to ingredients.
Refined query: "2 medium potatoes, 1 carrot, 1 onion, 200 g cooked lentils, 3 tomatoes, 1 tbsp tomato paste; I want a thick stew; for two; 30 minutes".
How to set restrictions and preferences
The "Preferences and restrictions" field allows excluding unwanted products or taking dietary requirements into account. For example, "gluten-free", "dairy-free", "vegetarian", "not spicy". If you have an allergy, be sure to state it explicitly. The tool does not check safety, so the final decision is always yours.
In addition to dietary restrictions, you can describe taste preferences: "I love spices", "I cannot stand cilantro", "I want hearty but not fatty". This helps the model choose suitable spices and cooking methods. Do not overload the field with dozens of conditions — it is better to split refinements into several iterations.
Restrictions: "vegetarian, gluten-free, not spicy; I love spices, but no cilantro".
Adjusting time and number of portions
The "People or portions" and "Available time" fields directly affect the complexity of the recipe. If you specified "for two" and "30 minutes", the tool will suggest dishes that can be prepared in that time. But if the first result requires 45 minutes, clarify: "strictly 30 minutes, no long frying". You can also ask for "steps of 10 minutes each" to control the process.
If time is specified incorrectly, change it. For example, "I have 20 minutes for preparation and 15 minutes for cooking". This helps break the recipe into parallel steps. For larger portions specify the exact number of diners so the tool recalculates proportions. Remember that the model may make mistakes in calculations, so check the final quantities.
Clarification: "for two, strictly 30 minutes; preparation 10 minutes, cooking 20 minutes".
Checking the result: what to look for
After generation carefully read the recipe. Check that all ingredients from your list were used, there are no extra ones that you did not specify. Make sure the steps are logical: first chopping, then frying, then simmering. If any step is missing or described unclearly, return to the form and clarify the request.
Pay attention to time: if the total time exceeds the specified limit, ask to simplify. Also check whether spices comply with your restrictions. If the recipe has salt and pepper but you did not specify it, that is normal — basic seasonings are often added by default. But if you asked "no salt" make sure it is not there.
Check: in the recipe "Vegetable stew with lentils" 40 minutes are indicated, although you asked for 30. Clarify: "reduce time to 30 minutes by pre-soaking lentils or using canned".
Iterations: from draft to finished dish
Refinement is a cycle: generated, checked, refined, generated again. Do not try to get a perfect recipe on the first try. Start with a general request, then add details: exact grammes, order of actions, desired consistency. Each iteration should solve one specific problem.
For example, after the second request you got a stew, but it seems too liquid. Add to restrictions: "thick, like a stew, not a soup". If the taste seems bland, ask "add spices: paprika, turmeric, black pepper". You gradually approach a dish you will actually cook.
Iteration 3: "Make the stew thick, add paprika and turmeric, time 30 minutes, for two".
Tool limitations and responsibility
The tool is not a professional culinary adviser. It does not check product safety compatibility, does not take individual allergies into account and does not guarantee that the dish will taste good. All recommendations are for reference only. If you have serious health restrictions, consult a doctor or dietician.
Also remember that the model may make mistakes in proportions and time. Always evaluate the result critically. Do not use the tool for meal planning in medical conditions without consulting a specialist. Responsibility for preparing and consuming the dish lies with you.
Example restriction: the tool may suggest adding salt even if you did not specify it. If you have hypertension, clarify "no salt" and check the result.
Refining a recipe in the "What to cook" tool is a practical skill. Start with a simple request, then refine ingredients, restrictions, time and portions. Check each result for logic and compliance with your conditions. Remember that the tool does not replace culinary experience and medical recommendations. Use it as an inspiration and planning assistant, but the final decision is always yours. By following these steps, you will be able to turn an initial draft into a ready recipe that suits you.
Open tool: Recipe generator ↗Interface translations are machine-assisted and may need refinement.