pizza-mcp
Related Servers
Alternatives to pizza-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.452 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
- AlicenseAqualityCmaintenanceEnables AI assistants to convert raw and cooked weights for meat and poultry by cut and cooking method from USDA data, calculate how much raw meat to buy for cooked servings, and look up cooking yields and sample ranges.5MIT
- AlicenseAqualityCmaintenanceEnables 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
- AlicenseAqualityCmaintenanceEnables modeling of startup financings such as SAFEs, convertible notes, priced rounds, option pool top-ups, fees, and multi-step financing histories, returning pre- and post-round cap tables with per-holder dilution and fully diluted ownership as markdown plus structured JSON. All tools are read-only and deterministic, requiring no API keys or network access.61MIT
- AlicenseNot gradedqualityDmaintenanceTracks caffeine decay and predicts safe bedtimes using a half-life model. No external integrations needed, intake is passed as parameters.MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection or overlapping purpose. Its purpose (compute pizza dough ingredient doses with baker's percentages) is unambiguous.
The single name calculate_dough follows a clear verb_noun snake_case convention. With one tool there is no internal inconsistency, though the pattern cannot be stress-tested across a set.
The domain is a single self-contained calculation, so one comprehensive tool is proportionate rather than artificially split. It is slightly thin in that the yeast model, fermentation scheduling, and flour handling are all fused into one call instead of being composable pieces.
The tool covers the core dough lifecycle inputs: flour blends and percentages, hydration, salt, yeast type, yeast forcing, fermentation time/temperature, and ball count/weight. Minor gaps exist, such as no reverse calculation (given yeast %, derive timing), no unit or temperature-scale conversion, and no output of a full step-by-step schedule.