Skip to main content
Glama

Raw to Cooked Weight MCP

Calculate raw meat to buy

calculate_raw_weight_to_buy
Read-onlyIdempotent

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).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "servings": "<servings>"
    },
    "name": "calculate_raw_weight_to_buy"
  }
}

Input Schema

NameRequiredDescriptionDefault
foodNoCut and species in plain words, for example "chicken thigh", "80/20 ground beef patty", "ribeye steak", "pork tenderloin", "bacon", "turkey breast", "bison burger".
unitNoUnit of cooked_serving_size: g, kg, oz or lb. Default oz.
methodNoCooking method: roast, grill, braise, simmer, pan_fry, pan_broil, deep_fry, microwave. Plain words work too (grilled, baked, slow cooker, sauteed, boiled).
servingsYesNumber of servings, for example 8.
yield_idNoExact row id from find_cooking_yield or list_cooking_yields. Overrides food and method.
cooked_serving_sizeNoCooked weight per serving in the chosen unit. Default 3 oz or 85 g.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile needs no restating. The description adds genuine context by disclosing the USDA cooking-yield basis and the default 3 oz (85 g) serving, but it says nothing about fallback behavior when the cut or method is unrecognized, or about what the result contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence that front-loads the core question being answered and tucks the default serving size at the end where it belongs. Nothing is wasted, though the one sentence carries the whole definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters, no output schema, and a nontrivial yield-lookup concept, the description is adequate but thin: it does not say whether the response includes the yield used, the cut that was matched, or a confidence/fallback indicator. Schema coverage compensates for inputs, but the return side is entirely unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; each parameter including yield_id's 'overrides food and method' note is already documented in the schema. The description only reinforces the default serving size, adding no new meaning about how food/method and yield_id interact.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb-and-resource framing: it computes how much raw meat or poultry to buy to yield a given number of cooked servings, keyed to the USDA cooking yield for the cut and method. That is concrete enough to distinguish it from a plain unit conversion, but it never names or contrasts the siblings (convert_cooked_to_raw, find_cooking_yield) that an agent will be choosing between.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the wording makes clear this is the tool for 'how much do I buy' planning, but there is no explicit when-to-use, when-not-to-use, or pointer to convert_cooked_to_raw / find_cooking_yield as alternatives. An agent must infer the routing from the purpose sentence alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.