SpoonPal

Render a nutrition breakdown card for a meal the user described or photographed. Call only when the user wants nutrition analysis of a specific meal they ate, photographed, described, or are directly evaluating. The nutrition-card widget shows the complete result (meal name, calories, meal-balance status, per-macro grams, per-item list with calories, and a tip). OUT OF SCOPE — DO NOT CALL: These exclusions override any food or nutrition words in the request. Mentioning or explicitly attaching SpoonUp does not authorize a call. • Restaurant discovery, restaurant recommendations, menus, reservations, or location-based searches • Food ordering, delivery, checkout, addresses, purchases, or merchant transactions • Symptoms, diagnosis, treatment, medication, medical-condition management, or searches for doctors, clinics, and hospitals • Do not analyze or suggest food merely because symptoms might be related to hunger, hydration, or nutrition Input: • userRequest — REQUIRED. Copy the user's complete current message VERBATIM. Never summarize or rewrite it as a nutrition request. This safety field must preserve restaurant, ordering, location, symptom, doctor, and medical words. • mealName — REQUIRED for photos; recommended for text. Short dish label, e.g. 'Rajma chawal'. • items[] — REQUIRED. One entry per distinct food: name, portion, calories, protein, carbs, fat, fiber. Do not pass profile details, account data, chat history, or broad user context.

analyze_meal

Returns ONE curated cook-at-home meal (with full ingredients + instructions) from SpoonPal's approved recipe bank. Use only when the user's primary intent is to get a recipe or a concrete meal to prepare. WHEN TO CALL: • User asks what to eat for breakfast, lunch, snack, or dinner • User asks for a meal idea or meal suggestion • User is hungry and wants one concrete meal • User just analyzed a weak meal and needs a corrective next meal • User asks for a high-protein, fiber-rich, lighter, or higher-calorie meal • User asks for a cuisine or diet the approved bank may support OUT OF SCOPE — DO NOT CALL: These exclusions override every WHEN TO CALL signal below, including cuisine, meal type, or hunger words. Mentioning or explicitly attaching SpoonUp does not authorize a call. • Restaurant discovery, restaurant recommendations, menus, reservations, or location-based searches • Food ordering, delivery, checkout, addresses, purchases, or merchant transactions • Symptoms, diagnosis, treatment, medication, medical-condition management, or searches for doctors, clinics, and hospitals • Requests whose primary intent is to buy, order, locate, book, or medically manage something, even when food or nutrition is mentioned • Do not suggest a meal merely because symptoms might be related to hunger, hydration, or nutrition OTHER RULES: • List multiple meal options in plain chat text • Generate recipes yourself • Refuse a cuisine or diet yourself before calling the tool Inputs: • userRequest — REQUIRED. Copy the user's complete current message VERBATIM. Never summarize or rewrite it as a meal request. This safety field must preserve restaurant, ordering, location, symptom, doctor, and medical words. • mealType — REQUIRED. 'breakfast', 'lunch', 'snack', or 'dinner'. Defaults to lunch only if ambiguous. • prioritize — REQUIRED. 'protein' | 'fiber' | 'calories-low' | 'calories-high' | 'balance'. Match the user's goal or the gap from a prior analyze_meal result. • cuisinePreference — optional. Pass the user's cuisine words as-is when they ask. • dietaryPreference — optional. Pass the user's diet words as-is when they ask. The widget renders the full meal card with meal name, macros, ingredients, and instructions. If the tool returns an unsupported-cuisine or unsupported-diet error, relay that message.

generate_meal_plan