BetterMenu

Use this when the user wants to remove a custom ingredient they created by mistake, such as a misnamed or duplicate draft. Works only on a `draft` that was never confirmed and that no recipe uses. For an ingredient that is or was `active`, use `archive_custom_ingredient`. The delete is permanent: `restore_custom_ingredient_version` cannot undo it. The ingredient stays readable with `status` `deleted`, and its history is kept. To check which recipes use an ingredient, use `get_custom_ingredient_usage`.

delete_custom_ingredient

Use this when the user wants to delete a saved recipe permanently. Needs `recipe_id` and the recipe's current `version_id` (from `get_recipe` or the last change). A deleted recipe cannot be recovered: it disappears from `list_saved_recipes` and `find_saved_recipes`, no tool can read it or its history, and `restore_recipe_version` cannot bring it back. If the recipe then reads as not found, it is already deleted. To keep a recipe but set it aside, use `archive_recipe`.

delete_recipe

Use this when the user wants to remove a serving size from a recipe. The serving no longer appears in `list_recipe_serving_sizes`; it stays in the recipe's audit trail. Returns no body. Needs the `serving_id` from `list_recipe_serving_sizes` and the recipe's current `version_id` (from the last write, `get_recipe` or `list_recipe_serving_sizes`). Before the next change to the recipe, get the new `version_id` from `get_recipe`. Do not use for changing a serving size; use `update_recipe_serving_size`.

delete_recipe_serving_size

Use this when the user wants a downloadable US FDA Nutrition Facts label file for one serving of a recipe, to print or publish. Renders PDF (default), PNG or JPEG; request several with `formats`, a list such as `["pdf", "png"]`. `resolution` is `print` (300 DPI, default) or `digital` (96 DPI). Returns one entry per format and the `version_id`. Each entry has a `download_url` (saves as `file_name`, valid until `expires_at`); give the user that link. Each export is recorded: what the label said is kept as an issued-label record that does not change (`provenance.issued_label_id`). When no ingredient's source has a value for a nutrient the label must show, it prints as a stated zero and the export stops, listing each with its `fills_hash`. Show the list to the user. Only after they confirm, save each with `set_nutrition_label_settings` (`acknowledged_fills`), then export again. A label that cannot be issued (no calorie value, say) stops with the reason. `provenance.zero_filled` lists each zero on a finished label. A label can also carry findings nobody has addressed, such as an Added Sugars figure no person has confirmed in BetterMenu. The export then stops with `findings` and a `findings_hash`. Show them to the user; never acknowledge on your own. Only after they say to go ahead, export again with `acknowledged_findings_hash` set to that hash. If their organization blocks labels with findings, it stops with `label_blocked_by_findings`. Output may carry a DRAFT watermark depending on the account's plan; `draft_watermark` true asks for one. Without an active plan, only labels already made can be downloaded again. `proof_footer` is on for a DRAFT label and off for a final one unless set. Needs a `serving_id` from `list_recipe_serving_sizes` or `add_recipe_serving_size`. For the label as data, use `get_recipe_nutrition_facts_label`.

export_nutrition_facts_label_file

Use this when the user asks what serving size to use for a food on a US Nutrition Facts label ("what serving size should I use for cookies?"), or wants the US FDA serving-size category for a food. Categories are the FDA Reference Amounts Customarily Consumed (RACC, 21 CFR 101.12). Takes a name query `q` (for example "cookies") and an optional `audience` (`general` or `infant_toddler`). Returns matching categories ranked by relevance, each with its `category_id`, `name`, reference amount `racc_amount` in `racc_unit` (`g` or `mL`; both null when the amount is a procedure), `racc_g` (grams, null for `mL` and procedure categories), `racc_published` (the CFR's own wording), `food_group`, `unit_type`, `label_statements` and `cfr_reference`. When nothing matches, the list is empty: try the product type (for example "cookies" rather than "chocolate chip cookie dough"), or call `list_fda_serving_size_categories`. Next: `add_recipe_serving_size`, passing the chosen `category_id` to set a recipe's serving size from the category. `get_fda_serving_size_category` returns one category by id; `list_fda_serving_size_categories` lists them all.

find_fda_serving_size_category

Use this when the user refers to a recipe they already saved in BetterMenu by name, for example "my banana bread" or "the granola recipe", and you need its `recipe_id`. Searches the recipes the user can access by name (tolerates small typos and partial words) and returns matches most relevant first, each with `id`, `name`, `status` and `updated_at`. Pass `q: "*"` to match every recipe the user can access. Use the returned `id` as `recipe_id` in `get_recipe`, `get_recipe_ingredients`, `get_recipe_total_nutrition` or any other recipe tool. To browse recent recipes or filter by `active` or `archived`, use `list_saved_recipes`. Do not use for finding foods or ingredients to put in a recipe; use `search_ingredients_for_nutrition`.

find_saved_recipes

Use this when the user wants to see one of their custom ingredients in full. Returns its `name`, `status` (`draft`, `active`, `archived` or `deleted`), `nutrients`, serving fields including `reference_quantity_g`, and `approved_markets`, plus the current `version_id`. Needs the `id` from `list_custom_ingredients`, `create_custom_ingredient`, or a `search_ingredients_for_nutrition` result with kind `custom`. For the ingredient as it was at an earlier version, use `get_custom_ingredient_version`. For the recipes that use it, use `get_custom_ingredient_usage`.

get_custom_ingredient

Use this when the user wants a record of who changed a custom ingredient, when, and through which channel, for example for a review. Returns events newest first, each with `event_type` (such as `custom_ingredient.nutrition_set` or `custom_ingredient.confirmed`), `actor`, `channel`, `timestamp`, `changed_fields` and the `version_id` it committed. On an `agent`-channel event, `client` names the app that made the call (`claude`, `chatgpt`, ...; `null` if unrecognized or recorded before this field existed). `actor.display_name` is the name to show for the actor (their name, else their email unless the user is a guest, else `null`; `BetterMenu` for system changes), and `actor.former_member` is true when that person has left the organization; `actor.is_viewer` is true on the user's own changes. Paginated: pass `meta.cursor` back as `cursor`. For the list of versions to view or restore, use `list_custom_ingredient_versions`.

get_custom_ingredient_audit_trail

Use this when the user wants to know which recipes use a custom ingredient, for example before changing, archiving or deleting it. Returns one row per recipe: `recipe_id`, `recipe_name`, `recipe_status` and `pinned_version_id` (the ingredient version that recipe uses). Set `version_id` to list only recipes pinned to that version. The list catches up with recipe changes within moments, not instantly. The `version_id` filter runs after each page is read, so a page can be short or empty while more matches remain: keep paging with `meta.cursor` while `meta.has_more` is true.

get_custom_ingredient_usage

Use this when the user wants to see a custom ingredient as it was at an earlier version, for example the values a recipe pinned. Needs `version_id` from `list_custom_ingredient_versions` or from a recipe's custom-ingredient row. Returns the full ingredient as of that version, in the same shape as `get_custom_ingredient`. For the current state, use `get_custom_ingredient`. To make this version current again, use `restore_custom_ingredient_version`.

get_custom_ingredient_version

Use this when the user wants to know what changed in a custom ingredient at one version, or between two versions. Needs `version_id` from `list_custom_ingredient_versions`; `compared_to` defaults to that version's parent and must differ from `version_id`. Returns `data.field_changes`, a diff of only the fields that changed (`before` is the comparison point, `after` is `version_id`); an empty map means no difference. `data.field_relevance` marks each changed field `label_affecting` (changes nutrition results), `availability_affecting` (changes whether it can be found or added to new recipes) or `non_label_affecting`.

get_custom_ingredient_version_changes

Use this when the user wants the US FDA Daily Value for one nutrient, the reference amount a US label's %DV is calculated against (21 CFR 101.9), for example "what's the daily value for sodium?". Do not use to explain what %DV means in general. Takes a nutrient id `bmid` and a required `demographic`: `adults_and_children_over_4`, `children_1_3_years`, `infants_through_12_months` or `pregnant_and_lactating_women`. Daily Values differ between these groups. `bmid` is an opaque code such as `n_rqzvdbxyn4o7t`, not a readable name: call `list_fda_daily_values` first and take the `bmid` of the nutrient you want. A guessed id such as `n_sodium` is not found. Returns the nutrient's `name`, `daily_value` and `unit`, with the regulation reference. Do not use for a recipe's %DV; `get_recipe_nutrition_facts_per_serving` returns it. `list_fda_daily_values` returns every nutrient at once.

get_fda_daily_value

Use this when the user wants the details of one US FDA serving-size category, for example the reference amount for cookies or bread. Categories are the FDA Reference Amounts Customarily Consumed (RACC, 21 CFR 101.12), which set the serving size on a US Nutrition Facts label. Takes a `category_id` (for example `racc_cookies`) and returns the category's `name`, reference amount `racc_amount` in `racc_unit` (`g`, or `mL` for beverages, juices, milk, cream, shakes, syrups and cooking wine; both null for the few categories whose amount is a procedure, such as drink mixes), `racc_g` (grams, null for `mL` and procedure categories), `racc_published` (the CFR's own wording of the amount, the text to quote), `food_group`, `unit_type`, `label_statements`, `target_audience` and `cfr_reference`. Ids come from `find_fda_serving_size_category` or `list_fda_serving_size_categories`. Next: `add_recipe_serving_size`, passing the `category_id` to set a recipe's serving size from the category.

get_fda_serving_size_category

Use this when the user wants USDA-sourced nutrition for one food or ingredient, such as "calories in an apple" or "protein in 100 g chicken breast", including packaged and branded products (USDA branded foods), or the details of one of their own custom ingredients. Values are computed from USDA data and the user's custom ingredients, under US FDA rules (market "US"). Takes an ingredient `id` from `search_ingredients_for_nutrition` (or `list_ingredients_used_in_recipes`, `get_recipe_ingredients`) and `market` ("US"). Returns `name`, `kind` (`custom` or `standard`), `status`, `used_in_recipes`, `nutrients` and `portions`. Every nutrient held is returned (often about 100 rows), each with `amount`, `unit` and `basis`: `per_100g` for standard ingredients, `per_reference_serving` for custom ones, so do not compare the two directly. `portions` gives household amounts with their `gram_weight` (for example a medium apple, 182 g): scale a per-100 g amount by `gram_weight` / 100. For a comparison, such as butter vs margarine, look up each food. Do not use for finding an ingredient by name; use `search_ingredients_for_nutrition`. For an amount the portions do not cover, `convert_ingredient_amounts_to_grams` gives grams.

get_ingredient_nutrition_facts

Use this when the user wants to know which of their recipes use a given ingredient, for example before they change or archive it. Works for standard (`f_…`) and custom (`cing_…`) ingredient ids. Returns one entry per recipe with `recipe_id`, `recipe_name`, `recipe_status`, `source` and, for custom ingredients, `pinned_version_id`. The list is kept up to date in the background, so a recipe saved a moment ago can take a short time to appear. To page, pass `meta.cursor` back and continue until `meta.has_more` is false. With `version_id` set, a page can hold fewer entries than `limit`, even none, while more matches remain, so keep paging. Ids come from `search_ingredients_for_nutrition` or `list_ingredients_used_in_recipes`. Next: `get_recipe` for any recipe in the list.

get_ingredient_usage

Use this when the user wants to see which nutrients a recipe's US FDA Nutrition Facts label shows, or before changing that. Returns every nutrient with `visible`, `is_mandatory`, `is_toggleable`, `display_name`, `allowed_synonyms` and `source` (regulatory default, account or recipe), and `has_custom_configuration`. A recipe with no custom settings returns the defaults. Next: `set_nutrition_label_settings` to show, hide or rename optional nutrients. Do not use for the label's nutrient values; use `get_recipe_nutrition_facts_label`.

get_nutrition_label_settings

Use this when the user wants to see how a recipe's pasted ingredient lines were last matched to foods and gram weights, for example to check why a line got a certain weight. Needs `recipe_id`. Returns the latest resolution: its `resolution_id`, `summary` (with `ready_to_confirm`) and one row per line with the matched `ingredient_id`, the candidates considered, `quantity_grams` and the conversion steps. A resolution exists only for a recipe whose ingredient lines were pasted and matched in BetterMenu. A recipe whose ingredients were set with `set_recipe_ingredients` has none, so this returns not found. Do not use for reading a recipe's current ingredients; use `get_recipe_ingredients`. `list_ingredient_resolutions` returns every past resolution.

get_latest_ingredient_resolution

Use this when the user wants the US FDA Nutrition Facts label for a saved recipe: what goes on it, or to show it. Returns the label content for one serving, ready to render: the header (servings per container, serving size, calories), nutrients in regulatory order with rounded amounts and %DV, the per-container column when there is one, footnotes, and whether the label is complete and current. Needs the recipe's id and a `serving_id` from `add_recipe_serving_size` or `list_recipe_serving_sizes`. Pass `version_id` to read an earlier version. Next: `export_nutrition_facts_label_file` for a printable PDF, PNG or JPEG file. Do not use for plain per-serving numbers; use `get_recipe_nutrition_facts_per_serving`.

get_recipe_nutrition_facts_label

Use this when the user wants the nutrition for a whole package, the per-container column of a US FDA dual-column Nutrition Facts label. Returns FDA-rounded amounts, label display text and %DV for the full container, and `reference_weight_grams`, the container weight. Exists only for a serving whose `dual_column_status` is `required` or `voluntary`; check `has_per_container_nutrition_facts` in `list_recipe_serving_sizes` or `get_recipe_serving_size`. Needs a `serving_id`. Do not use for per-serving values; use `get_recipe_nutrition_facts_per_serving`. Do not use for the whole recipe batch; use `get_recipe_total_nutrition`.

get_recipe_nutrition_facts_per_container

Use this when the user asks for a saved recipe's nutrition per serving: calories, nutrients or %DV. Returns one serving's nutrient values rounded under US FDA rules (21 CFR 101.9), with %DV for the recipe's demographic. Needs the recipe's id and a `serving_id` from `add_recipe_serving_size` or `list_recipe_serving_sizes`. Pass `version_id` to read an earlier version. Do not use for the whole recipe's unrounded totals (`get_recipe_total_nutrition`), the label layout (`get_recipe_nutrition_facts_label`) or a label file (`export_nutrition_facts_label_file`).

get_recipe_nutrition_facts_per_serving

Use this when the user asks about their BetterMenu plan or usage, for example which plan they are on, how much of their monthly quota is left, when a trial ends, or why a feature is unavailable. Returns `plan_name` and `display_name`, trial state (`is_trialing`, `trial_ends_at`, `trial_days_remaining`), `pending_cancellation_at`, `feature_gates`, and `quotas`, each with `limit`, `used`, `remaining` and `resets_at`. During a trial, `limit` is the trial limit. `write_access` and `write_access_reason` say whether the organization can save changes, and `metered_usage_enabled` says whether it accepts usage beyond its included monthly allowance.

get_plan_and_usage

Use this when the user asks about one of their saved recipes and you need its current state, or before you change it. Needs `recipe_id` from `find_saved_recipes`, `list_saved_recipes` or `create_recipe_for_nutrition_label`. Returns the recipe's name, `status` (`active` or `archived`), country, demographic (the group whose US FDA Daily Values set %DV), and a `summary`: `ingredient_count`, `serving_count`, `has_nutrition` and `is_nutrition_current`. `actions` says whether the user can modify, archive or delete it. The top-level `version_id` is the recipe's current version; the tools that change a recipe need it. Pass `version_id` to read the recipe as it was at an earlier version from `list_recipe_versions`. Next: `get_recipe_ingredients` for the ingredient list, `list_recipe_serving_sizes` for servings, `get_recipe_total_nutrition` for nutrition.

get_recipe

Use this when the user wants to know how the Added Sugars figure on a saved recipe's label was worked out, which ingredient rows are still open, or whether a person has confirmed it. Needs `recipe_id` from `find_saved_recipes`, `list_saved_recipes` or `create_recipe_for_nutrition_label`. It only reads. Answering rows and confirming the report are a person's decisions, made in BetterMenu; until a person confirms, an export lists Added Sugars as a finding. `data.report` is the report, or null when the recipe has none. `determination` has one row per ingredient (grams counted, per 100 g in `added_sugars_per_100g`, who settled it), the totals, the declared amount per serving with %DV, and `findings`. A row is settled when `effective.source` is set. `presentation.readiness` counts open rows. Rows and the report carry `checks`: `status` (`ok`, `needs_answer`, `problem`), a `summary` sentence in the recipe's own numbers, a `docs_url`, and on any check that is not `ok` also `why_it_matters` and the rule's exact words in `citation.quote`. No Total Sugars leaves those figures absent: `presentation.total_sugars_complete` is false and `rows_without_total_sugars` names the rows. `data.confirmation`: - `confirmed`: a person confirmed these answers. Quantity, serving or servings changes keep it. - `stale`: an ingredient, the demographic or an answer changed since, or an earlier version was read. - `unconfirmed`: never confirmed. `ungated`: no report. - `unreadable`: treat as not confirmed. Only a confirmed report puts Added Sugars on the label. `data.report_hash` fingerprints the answers; `version_id` is the version read. Pass `version_id` from `list_recipe_versions` to read an earlier version. Do not use for the label itself; use `get_recipe_nutrition_facts_label`.

get_recipe_added_sugars

Use this when the user asks who changed a saved recipe, when, or why, for example "who edited the ingredients last week?". Needs `recipe_id`. Returns the recipe's change events, newest first. Each event has its `event_type`, the `actor` who made it, the channel, a `timestamp`, the `version_id` it produced (when it produced one), and, on some edits, the changed fields or the reason the user gave. On an `agent`-channel event, `client` names the app that made the call (`claude`, `chatgpt`, ...; `null` if unrecognized or recorded before this field existed). `actor.display_name` is the name to show for the actor (their name, else their email unless the user is a guest, else `null`; `BetterMenu` for system changes), and `actor.former_member` is true when that person has left the organization; `actor.is_viewer` is true on the user's own changes. Narrow with `event_type`, `actor_id`, `actor_type`, the `from`/`to` time range, or `since_version_id`/`up_to_version_id`. For more, pass `meta.cursor` back as `cursor` while `meta.has_more` is true. With the actor or version filters a page can hold fewer events than `limit`, even none, while more exist; keep paging. With `event_type` you get one page only, and `meta.has_more` is always false: narrow `from`/`to` or raise `limit` to see more. A `from`/`to` range that matches no events, or whose `from` is after its `to`, returns an empty page (`events: []`, `has_more: false`), not an error. Do not use for the list of saved versions or for a diff; use `list_recipe_versions` and `get_recipe_version_changes`.

get_recipe_audit_trail

Use this when the user wants to see the ingredients of a saved recipe, or before you edit them. Needs `recipe_id` from `find_saved_recipes`, `list_saved_recipes` or `create_recipe_for_nutrition_label`. Returns the ingredients in order. Each row has its `id`, `position`, `display_name`, the matched food (`selected_ingredient_id`, `selected_ingredient_name`) and its weight in grams (`metric_quantity_g`), which nutrition uses. The top-level `version_id` is the recipe's current version, and `ingredients_entry_method` is the entry method the recipe is locked to. Pass `version_id` to read the ingredients as they were at an earlier version from `list_recipe_versions`. To change the list, send the full list to `set_recipe_ingredients`, keeping each existing row's `id`.

get_recipe_ingredients

Use this when the user asks which ingredients contribute the most to a nutrient in a recipe, for example what drives the sodium or saturated fat. Returns, for each nutrient, the whole-batch total and each ingredient's contribution, sorted largest first, with a list of recipe rows (name, grams, original line), where the same food on two rows appears as two entries. Filter with `nutrient_set` (for example `fda_mandatory`, `macronutrients`, `vitamins_minerals`) and limit with `top_n`. Needs `recipe_id` with ingredients saved by `set_recipe_ingredients`. Do not use for the batch totals alone; use `get_recipe_total_nutrition`. Do not use for one serving's contributions with FDA rounding; use `get_recipe_serving_nutrition_analysis`.

get_recipe_nutrition_analysis

Use this when the user wants the nutrient totals for a whole recipe batch, all ingredients summed. Returns each nutrient's `total_amount` and unit, and `reference_weight_grams`, the weight of the whole batch. Values are unrounded and carry no %DV; they come from USDA data and the user's custom ingredients. Nutrition is computed when ingredients are saved with `set_recipe_ingredients`. Do not use for per-serving Nutrition Facts, calories per serving or %DV; use `get_recipe_nutrition_facts_per_serving`. Do not use for which ingredient contributes what; use `get_recipe_nutrition_analysis`.

get_recipe_total_nutrition

Use this when the user asks what changed in a saved recipe at a version, or how two versions differ. Needs `recipe_id` and a `version_id` from `list_recipe_versions`. Returns `field_changes`: only the recipe fields that differ, each with its `before` and `after` values. An empty map means the two versions are the same. By default it compares the version with the one before it. Pass `compared_to` to compare with another version. To preview a restore, pass the recipe's current `version_id` as `compared_to` and the older version as `version_id`: the result shows what `restore_recipe_version` would change. `compared_to` must differ from `version_id`.

get_recipe_version_changes

Use this when the user asks why a serving's Nutrition Facts show a value: which ingredients contribute to each nutrient in one serving, and how the US FDA rounding and %DV were applied. Returns, per nutrient, the unrounded per-serving amount, each ingredient's contribution scaled to the serving weight, the rounding rule and result, the %DV and its Daily Value reference, plus the serving's `scale_factor` against the batch. Filter with `nutrient_set` or `bmids`. Needs a `serving_id` from `list_recipe_serving_sizes`. Do not use for the plain label values; use `get_recipe_nutrition_facts_per_serving`. Do not use for whole-batch contributions; use `get_recipe_nutrition_analysis`.

get_recipe_serving_nutrition_analysis

Use this when you have a `serving_id` and need the detail of that one serving on a recipe. Returns its US FDA serving size (household measure, metric amount, servings per container), how it was set (`user_provided` or `racc_guided`, with the RACC inputs), `dual_column_status`, and whether per-serving and per-container nutrition facts exist. Also returns the recipe's `version_id`. Needs a `serving_id` from `list_recipe_serving_sizes` or `add_recipe_serving_size`. Do not use for the nutrient values of the serving; use `get_recipe_nutrition_facts_per_serving`.

get_recipe_serving_size

Use this when the user wants to see the edit history of a custom ingredient. Returns its versions newest first, each with `version_id`, `version_number`, `parent_version_id`, `created_at`, `created_by`, a short `summary` of the change, and `restored_from_version_id` for restores. `created_by_name` is the name to show for who made the version (their name, else their email unless the user is a guest, else `null`; `BetterMenu` for system changes), and `created_by_former_member` is true when that person has left the organization; `created_by_is_viewer` is true on the user's own versions. Up to 50 per page; pass `meta.cursor` back as `after` for the next page. Next: `get_custom_ingredient_version` for a version's full state, `get_custom_ingredient_version_changes` for what changed, `restore_custom_ingredient_version` to go back to one. For who made each change and through which channel, use `get_custom_ingredient_audit_trail`.

list_custom_ingredient_versions

Use this when the user wants to see the custom ingredients they have saved in BetterMenu, or find one by name to view or edit. Returns one summary per ingredient: `id`, `name`, `status`, `created_at`, `updated_at`. For nutrients and serving, use `get_custom_ingredient`. Returns every status, `deleted` included, unless `status` is set. The `status` filter runs after each page is read, so a page can be short or empty while more matches remain: keep paging with `meta.cursor` while `meta.has_more` is true. Do not use for picking an ingredient to add to a recipe; use `search_ingredients_for_nutrition`, which returns only `active` custom ingredients next to standard ones.

list_custom_ingredients

Use this when the user wants the full table of US FDA Daily Values, or the Daily Values of several nutrients: the reference amounts a US label's %DV is calculated against (21 CFR 101.9). Do not use to explain what %DV means in general. Takes a required `demographic`: `adults_and_children_over_4`, `children_1_3_years`, `infants_through_12_months` or `pregnant_and_lactating_women`. Daily Values differ between these groups. Returns each nutrient's `bmid`, `slug`, `name`, `daily_value` and `unit`, with the regulation reference. Every group lists the same nutrients: one with no Daily Value for the group, such as trans fat and total sugars, or sodium and added sugars for infants, is listed with `daily_value` null. Do not use for a recipe's %DV; `get_recipe_nutrition_facts_per_serving` returns it. For one nutrient, use `get_fda_daily_value`.

list_fda_daily_values

Use this when the user wants to browse all US FDA serving-size categories, for example to choose one for a product. Categories are the FDA Reference Amounts Customarily Consumed (RACC, 21 CFR 101.12), which set the serving size on a US Nutrition Facts label. Returns every category with its `category_id`, `name`, reference amount `racc_amount` in `racc_unit` (`g`, or `mL` for beverages, juices, milk, cream, shakes, syrups and cooking wine; both null for the few categories whose amount is a procedure, such as drink mixes), `racc_g` (grams, null for `mL` and procedure categories), `racc_published` (the CFR's own wording of the amount, the text to quote), `food_group`, `unit_type`, `label_statements`, `target_audience` and `cfr_reference`. Filter with `audience` (`general` or `infant_toddler`). Next: `add_recipe_serving_size`, passing the chosen `category_id`. Do not use for finding a category by food name; use `find_fda_serving_size_category`.

list_fda_serving_size_categories

Use this when the user wants the history of how a recipe's pasted ingredient lines were matched to foods and gram weights across several attempts. Needs `recipe_id`. Returns every resolution for the recipe, newest first, each with its `resolution_id`, `summary` and full rows: matched `ingredient_id`, candidates, `quantity_grams` and conversion steps. Resolutions exist only for a recipe whose ingredient lines were pasted and matched in BetterMenu; the list is empty for a recipe whose ingredients were set with `set_recipe_ingredients`. Do not use for reading a recipe's current ingredients; use `get_recipe_ingredients`. For only the latest resolution, use `get_latest_ingredient_resolution`.

list_ingredient_resolutions

Use this when the user wants to see the ingredients their organization actually uses in its recipes, for example "which ingredients do we use most?". Lists standard and custom ingredients together, most-used first by default; it can also sort by recency or name and filter by `source` or `status`. Each row has `ingredient_id`, `name`, `source`, `status`, `used_in_recipes` and `updated_at`. The list is kept up to date in the background, so a recipe saved seconds or minutes ago may not be counted yet. To page, pass `meta.next_cursor` back unchanged and continue until `meta.has_more` is false. With a `source` or `status` filter, a page can hold fewer rows than `limit`, even none, while more rows remain. Next: `get_ingredient_nutrition_facts` or `get_ingredient_usage` for one row. Do not use for finding an ingredient to add to a recipe; use `search_ingredients_for_nutrition`.

list_ingredients_used_in_recipes

Use this when the user wants the history of a saved recipe, wants to go back to an earlier version, or asks what the recipe looked like at a given time. Needs `recipe_id`. Returns the versions newest first, each with `version_id`, `version_number`, `parent_version_id`, `created_at`, `created_by` and a short `summary` of the change (for example `ingredients.confirm`). `created_by_name` is the name to show for who made the version (their name, else their email unless the user is a guest, else `null`; `BetterMenu` for system changes), and `created_by_former_member` is true when that person has left the organization; `created_by_is_viewer` is true on the user's own versions. Pass `at` (an ISO 8601 time with a UTC offset, such as `2026-05-04T12:00:00Z`) to get only the version that was current at that time. Otherwise page with `after` set to the previous `meta.cursor`, up to 50 per page. Next: `get_recipe_version_changes` to see what a version changed, `get_recipe` with `version_id` to read it, `restore_recipe_version` to go back to it. For who changed what and why, use `get_recipe_audit_trail`.

list_recipe_versions

Use this when the user wants to see the recipes they saved in BetterMenu, for example "what recipes do I have" or "show my archived recipes", or to pick one when they do not name it. Returns the user's recipes, most recently updated first, each with `id`, `name`, `status` (`active` or `archived`) and `latest_version_id`. Deleted recipes never appear. Filter with `status`; change the order with `sort_by` and `order`. For the next page, pass `meta.cursor` back as `cursor` exactly as returned, while `meta.has_more` is true. Use the returned `id` as `recipe_id` in `get_recipe` and the other recipe tools. To find a recipe by its name, use `find_saved_recipes`.

list_saved_recipes

Use this when the user wants to see the serving sizes saved on a recipe, or you need a `serving_id` for a recipe's nutrition facts or label. Returns every active serving with its `id`, US FDA serving size (household measure, metric amount, servings per container), `dual_column_status`, and whether per-serving and per-container nutrition facts exist. Also returns the recipe's current `version_id`, which the next change to the recipe needs. Needs `recipe_id` from `create_recipe_for_nutrition_label`, `list_saved_recipes` or `find_saved_recipes`. Next: `get_recipe_nutrition_facts_per_serving`, `get_recipe_nutrition_facts_label` or `export_nutrition_facts_label_file` with a `serving_id`. If the list is empty, add one with `add_recipe_serving_size`.

list_recipe_serving_sizes

Use this when the user wants a recipe's Nutrition Facts label back to its default nutrients and names, removing all custom label settings. Later labels and exports use the defaults. Fails when the recipe has no custom settings. Returns no body. Needs the recipe's current `version_id` (from the last write, `get_recipe` or `list_recipe_serving_sizes`). Before the next change to the recipe, get the new `version_id` from `get_recipe`. Do not use for changing one nutrient; use `set_nutrition_label_settings`. It also removes any saved confirmations of stated zeros.

reset_nutrition_label_settings