Skip to main content
Glama

Kitchen: cooking temperatures, storage times, baking math, ratios and swaps

check_kitchen
Read-only

Returns kitchen figures in F and C: the federal minimum internal temperature for poultry, ground meat, beef, bison, goat, pork, lamb, veal, ham, rabbit, venison, fish, egg dishes and leftovers with rest times, and a shellfish visual check that has no number; fridge and freezer keeping times for about 40 foods; the curing-salt limit (the federal 156 ppm figure only); the high-altitude boiling point. Trade-practice answers are labelled as trade practice: brine and quick-pickle ratios, coffee and tea ratios, baker's percentages, recipe scaling, and ingredient swaps with allergy flags and a one-line why. Topic is temperature, storage, baking, ratio or substitute, and is inferred from the query when topic is omitted. Applies to questions about minimum internal cooking temperatures, how long food keeps, baking math, brine, coffee or tea ratios, or an ingredient swap. The figures are cooking guidance, not a nutrition panel or a recall notice. Results report what the official sources say and are not a safety assessment. Not medical advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_kitchen"
  }
}

Input Schema

NameRequiredDescriptionDefault
foodNoThe food, tea type or ingredient, e.g. 'chicken', 'salmon', 'buttermilk', 'green tea'
kindNoFor baking: scale, percent (baker's percentages and hydration) or altitude. For ratio: wet_brine, dry_brine, pickle, cure, coffee or tea
unitNoUnit for amount: g, kg, oz, lb, ml, l, tsp, tbsp, cup or floz
avoidNoAllergens to avoid; swaps that list them are flagged and sorted last
queryNoThe question in the person's words, e.g. 'how long does cooked rice keep'
topicNoWhich kind of answer; inferred from query or the other fields when left out
amountNoFor ratios: the water or liquid (brine, pickle, coffee, tea) or the meat weight (dry brine, cure)
factorNoScale factor, e.g. 1.5
reading_cNoA thermometer reading in C to compare with the food's minimum
reading_fNoA thermometer reading in F to compare with the food's minimum
altitude_mNoAltitude in metres
altitude_ftNoAltitude in feet
ingredientsNoFor baking scale or percent: the recipe's ingredients with amounts. Weigh flour and water in g, oz or lb for percentages
to_servingsNoServings wanted
from_servingsNoServings the recipe makes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuinely new behavioral context: answers are labelled 'trade practice' vs official, the shellfish visual check has no numeric figure, the curing-salt figure is the federal 156 ppm only, and results are 'what the official sources say' rather than a safety assessment. That framing matters for a guidance tool, though it does not describe result shape or how multiple topics combine in one response.

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

Conciseness3/5

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

The lead is front-loaded and the trade-practice disclaimer is well placed, but the enumeration of thirteen meat types and 'about 40 foods' is padding that does not help selection. The disclaimer tail ('not a nutrition panel', 'not a safety assessment', 'Not medical advice') is three near-redundant negative statements where one would do.

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

Completeness4/5

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

For a 15-parameter, zero-required, no-output-schema tool the description does the essential work: it tells the agent what domains exist, that topic can be omitted and is inferred, and what the answers are and are not. What it lacks is any hint of the response shape or how a partial call (e.g. only `query`) resolves, which an agent would need for a tool with no required parameters.

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 every one of the 15 parameters is already documented with units, ranges and examples. The description adds only the topic-inference behavior, which the schema also states, and otherwise restates the domain of `kind` and `topic` without new constraints or typical combinations.

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?

The opening sentence names the resource (kitchen figures in F and C) and enumerates the exact domains covered: minimum internal temperatures, fridge/freezer keeping times, curing-salt limits, boiling point, and trade-practice ratios and swaps. It also draws explicit boundaries against siblings — 'not a nutrition panel or a recall notice' clearly separates it from check_food and check_recalls, and 'not medical advice' from check_illness/check_medicine.

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

Usage Guidelines4/5

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

It states the triggering question types plainly ('questions about minimum internal cooking temperatures, how long food keeps, baking math, brine, coffee or tea ratios, or an ingredient swap') and tells the agent that topic is inferred when omitted. It excludes nutrition and recall questions but does not name the sibling tools to route to, so the agent must infer the handoff rather than being told.

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.

Resources