raw-to-cooked-weight-mcp
Related Servers
Alternatives to raw-to-cooked-weight-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to convert recipe amounts between volume and weight for specific ingredients using measured densities, scale recipes, and convert oven temperatures, with source citations and alternative published values.4318 npmMIT
- AlicenseAqualityCmaintenanceReturns USDA-derived edible yield, refuse percent and trim waste for 305 raw fruits and vegetables, letting an assistant convert between as-purchased and edible weights. It also answers how many whole items or how much produce to buy for a recipe amount given in grams, pounds, cups or household measures.4MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to calculate recipe and per-serving calories, macros, and FDA-rounded Nutrition Facts values from ingredient lines using USDA FoodData Central data, including scaling recipes and looking up ingredient nutrition.4MIT
- AlicenseAqualityBmaintenanceEnables deterministic recipe and portion math with USDA-sourced macros, gram conversions, cooked yields, and per-eater portions.12MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to answer food safety and shelf-life questions using USDA-grade data, with tools for shelf life, safety checks, storage tips, and waste cost calculations.647 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to search recipes, compose nutritionally balanced meals, optimize weekly meal plans based on macro targets for family members, and generate consolidated grocery lists from a personal recipe database.-
TDQS
Scored across 5 tools
The direction-based converters (raw→cooked vs cooked→raw) are clearly distinguished by name and description, and find vs list have distinct intents (single precise lookup with yield_id alternatives vs filtered browsing). The only mild overlap is between calculate_raw_weight_to_buy and convert_cooked_to_raw, since both produce a raw weight for cooked amounts, but the servings-scaling framing mostly separates them.
All names are snake_case, verb-first, and descriptive (convert_*, calculate_*, find_*, list_*). The pattern is predictable, though the two converts embed a directional argument (raw_to_cooked) rather than a pure verb_noun object, which is a minor deviation.
Five tools is well-scoped for a focused weight-conversion domain, with no filler. Each tool covers a distinct step: two directions of conversion, a batch/purchase calculator, a precise yield lookup, and a browse/list operation.
Coverage of the core lifecycle (raw→cooked, cooked→raw, servings→purchase amount, yield lookup and browsing) is solid and closes most workflows. Minor gaps remain: no inverse of calculate_raw_weight_to_buy (cooked weight → number of servings) and no way to scale nutrition per portion, but agents can work around these with the existing converters.