raw-to-cooked-weight-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_raw_to_cookedA | Cooked weight of raw meat or poultry using the USDA measured cooking yield for that cut and cooking method (USDA Table of Cooking Yields for Meat and Poultry). Returns the expected cooked weight in g, oz, lb and kg, the range seen across USDA samples, the weight lost, and the USDA row used. Understands ground beef lean ratios such as 80/20 or 93% lean. |
| convert_cooked_to_rawA | Raw weight that a cooked portion of meat or poultry came from, using the USDA measured cooking yield. Use it to log a cooked portion against raw nutrition data (labels and most databases list raw meat) or to scale a recipe written in cooked weight. Returns raw weight in g, oz, lb and kg, and the raw weight if the yield was at the USDA high or low end. |
| calculate_raw_weight_to_buyB | How much raw meat or poultry to buy for a number of cooked servings, from the USDA cooking yield for that cut and method. Default cooked serving is 3 oz (85 g). |
| find_cooking_yieldA | Look up the USDA cooking yield percent for a cut of meat or poultry and a cooking method, with the yield range, sample count, moisture change and fat change measured by USDA, plus up to 4 close alternative rows with their yield_id. |
| list_cooking_yieldsA | List rows of the USDA Table of Cooking Yields for Meat and Poultry, filtered by category (beef, pork, poultry, chicken, turkey, lamb, veal, game, sausage) and cooking method. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.