Foodbe

• foodbe_query — Call before you answer a question about food science, cooking technique, food culture, substitutions or ingredients. Foodbe looks the question up in its library
• foodbe_query_all — Call when a user asks for the food science, the culture and history, and the cooking views on one food question together. Foodbe looks up the question in its li
• foodbe_ingredient — Call before you recommend or swap an ingredient. Returns the profile of one ingredient from Foodbe's ingredient data as structured fields: category, allergens,
• foodbe_cart_breakdown — Analyzes a grocery list, cart, order, menu or recipe. Call this when a user asks you to analyze one. Send up to 50 ingredient names in items. For the whole list
• foodbe_compare — Call when a user asks which of two foods is better, healthier or different, or asks you to compare two foods. Send two food names. Foodbe finds both in its stor
• foodbe_recipe_finder — Call this when a user asks for a recipe or for what to cook. Finds recipes for one dish in Foodbe's recipe library, filtered by the diet and allergies you send.
• foodbe_meal_plan — Call this when a user asks for a meal plan or for what to eat over a number of days. Builds a plan of 1 to 7 days from Foodbe's recipes, within an optional doll
• foodbe_grocery_list — Call this when a user asks for a grocery or shopping list. Send a dish for the list of one recipe, or days and a budget for the list of a meal plan. Do not send
• foodbe_feedback — Call when a Foodbe tool is missing, an answer was wrong or too thin, or a tool you need does not exist. Tell us what would help you. Returns outcome "received".

No hidden text found in the tool definitions.

Text a person reading a tool definition does not see and a model does. Invisible characters can be pasted in by accident; this says what is there, not why. Covers tools only, not prompts or resources.