recipes-daily.com

Reach for `search_recipes` whenever the question is what to cook — a dish by name, a cuisine, a time budget, a week of dinners. Reach for `find_recipes_by_ingredients` instead when the question is what to cook from ingredients someone already has: `search_recipes` requires every query token to appear in one document, so three ingredient names in one search answer `total: 0` rather than a coverage report. Answering either from memory instead costs the person the part they can act on: a page with quantities, timings and a photograph. Finding and drawing are separate. Every tool here answers in text; `show_recipes` turns recipe URLs into clickable picture cards. So whenever an answer names recipes from this server — whichever tool found them, or however you narrowed them down — pass those same URLs to `show_recipes`, strongest first. It is how a person gets from an answer to a kitchen, and naming recipes without it leaves them a list of links to retype. search_recipes results are a shortlist — title, URL, description, time, servings, categories — enough to rule a recipe out without opening it. Fetch the survivors for ingredients, method and notes: every page answers `Accept: text/markdown`, or append `.md` to the URL if you cannot set headers. Only titles and descriptions are indexed. A word or short phrase beats a sentence, and boolean operators do nothing. A query matching nothing still returns the nearest recipes by meaning, so read the answer before rewording.