Skip to main content
Glama
Kitchen Pass MCP server

Kitchen Pass MCP server

Official

Yield and cost from a purchase (paid, $0.01)

calculate_yield_and_cost
Destructive

Calculate usable and cooked yield plus cost per kg and per portion from an ingredient's purchased weight and price, so you can turn trim and cook loss into portion costs.

Instructions

Raw vs cooked weight and cost per portion: what a brisket, lamb leg or snapper yields after trim and cook loss, from head chef Cristopher's verified ranges. Send ingredient, weight bought, price paid, optional portions; get usable and cooked weight (best/mid/worst), cost per kg and per portion, with workings. 30+ items: beef, lamb, pork, chicken, seafood, vegetables, fruit. Refused, never guessed: allergen, curing and preserving terms. Only a 200 answer is charged; refusals and 404s are free.

Use when the user already bought, or has priced, a weight of one ingredient and wants what it yields and the cost per portion. For "how much do I need for N people", use calculate_amount_to_buy instead. ingredient must be an exact listed name or alias (others get a free 404 with suggestions). price is the total paid for purchased, not a price per kg. Give either portions (split the yield into N) or portionSize, not both. currency is required: the user's 3-letter currency code (display only). Costs $0.01. Paid automatically in USDC with x402 (test USDC when this server is set to base-sepolia), within this server's per-session and per-day spend caps. Only a 200 answer is charged; 400, 404 and 422 are free. Set dryRun to true to check for free whether this would be answered and what it costs; nothing is signed. If unsure what is covered, call check_coverage first (free). Not every answer is chef-verified: say "chef-verified by Cristopher" only when the result's label says exactly that; otherwise say it is not chef-verified. A refusal is final: don't rephrase the question to get around it.

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": {
      "ingredient": "<ingredient>",
      "purchased": "<purchased>",
      "price": "<price>",
      "currency": "<currency>"
    },
    "name": "calculate_yield_and_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYesTotal paid for the purchased quantity.
dryRunNoFree quote only: check whether this would be answered and what it costs. Nothing is signed or charged.
currencyYesThe user's 3-letter currency code, e.g. AUD, USD, GBP. Display only.
portionsNoSplit the yield into this many portions: cooked when the chef has a cook-loss range for the ingredient, otherwise trimmed raw (`basis` says which). Not with portionSize.
purchasedYesBetween 1 g and 10 t in total (0.0353 oz to 22,046 lb; lb and oz are converted exactly).
ingredientYes
portionSizeNoWeight of one portion as served: cooked when the chef has a cook-loss range for the ingredient, otherwise trimmed raw (`basis` says which). Not with portions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Far beyond the annotations: it discloses the $0.01 charge, that only 200 responses are billed while 400/404/422 and refusals are free, automatic USDC/x402 payment subject to session and daily spend caps, free dryRun quotes, and that refusals are final and never guessed for allergen/curing/preserving terms. Minor gap: it does not explain why destructiveHint=true is set (presumably the monetary charge), so an agent must infer the side effect is payment rather than data change.

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?

Front-loaded with the outcome first, then usage, then payment mechanics, and most sentences carry distinct information. It loses a point for repeating the billing rule verbatim ('Only a 200 answer is charged; refusals and 404s are free' appears twice) and for a fairly dense block of payment detail.

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

Completeness5/5

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

There is no output schema, and the description compensates by describing the return shape: usable and cooked weight at best/mid/worst, cost per kg and per portion, plus workings. With the charging, refusal, and verification-labeling rules included, an agent has everything needed to call and interpret the result.

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

Parameters4/5

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

Schema coverage is 86%, so the baseline is 3; the description adds genuine meaning on top by clarifying price is the total paid rather than a per-kg rate, currency is display-only, and ingredient must match an exact listed name or alias or a free 404 with suggestions is returned. It largely restates the schema's portions/portionSize mutual exclusion, so it stops short of 5.

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

Purpose5/5

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

States a concrete verb and resource ('raw vs cooked weight and cost per portion'), names the inputs and outputs, and explicitly contrasts with calculate_amount_to_buy for the reverse question. An agent can distinguish it from every listed sibling without opening the schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use condition (user already bought or priced a weight of one ingredient), names the alternative for the opposite question, and adds routing rules: call check_coverage when unsure, use dryRun for a free check, ingredient must be an exact listed name or alias, and give either portions or portionSize, not both.

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