Skip to main content
Glama

BRAINIAC Restaurant Operations Intelligence

Normalize recipe yields

restaurant-operations_recipe-yield-normalize
Read-onlyIdempotent

Normalize recipe line quantities into ingredient units and per-portion amounts using accurate mass and volume conversions. Price $0.04 USDC. POST /api/v1/restaurant-operations/recipe-yield-normalize. An unpaid call returns the x402 payment terms and does not run.

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": "restaurant-operations_recipe-yield-normalize"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNocsv, string, length 0 to 200000. Optional.
asOfNoasOf, string, length 0 to 40. Optional.
fileNofile, object. Optional.
jsonNojson, string, length 0 to 200000. Optional.
textNotext, string, length 0 to 200000. Optional.
salesNosales, array. Optional.
wasteNowaste, array. Optional.
matrixNomatrix, array. Optional.
pricesNoprices, array. Optional.
recipesNorecipes, array. Optional.
allergensNoallergens, array. Optional.
ingredientsNoingredients, array. Optional.
recipeLinesNorecipeLines, array. Optional.

Output Schema

NameRequiredDescriptionDefault
itemsNoitems. Array.
statusNostatus. String.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
priceInventedNopriceInvented. Boolean.
allergenInventedNoallergenInvented. Boolean.
nutritionInventedNonutritionInvented. Boolean.
foodSafetyComplianceClaimedNofoodSafetyComplianceClaimed. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, and the description adds genuinely non-structured context: a $0.04 USDC price, the POST endpoint, and the crucial fact that an unpaid call returns x402 payment terms and does not execute. That payment-gating disclosure is the kind of behavior an agent cannot get from annotations, though no throughput or input-size caveats are mentioned.

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

Conciseness5/5

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

Three short sentences: capability first, then price, then endpoint and payment failure mode. Zero filler and the most decision-relevant constraint (unpaid calls do not run) is stated plainly.

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?

An output schema exists, so return values need no explanation, and the payment path is fully described. For a 13-parameter nested tool with all-optional inputs the description is a bit thin on which arrays actually drive the normalization, but the billing and endpoint details close the main gaps.

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 all 13 parameters (recipes, recipeLines, ingredients, prices, sales, waste, allergens, matrix, plus csv/json/text/file/asOf payloads) are documented structurally. The description only gestures at recipeLines and portion/yield semantics without clarifying which input sets are required to produce meaningful output, so it lands at the baseline.

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?

States a specific verb and resource: normalize recipe line quantities into ingredient units and per-portion amounts, with the mechanism named (mass and volume conversions). An agent can distinguish this from siblings like recipe-cost-calculate or food-cost-report, though the description never explicitly contrasts them.

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 only implied by the domain vocabulary (recipe lines, portions, ingredient units); there is no explicit statement of when to pick this over recipe-cost-calculate or food-waste-estimate, nor any prerequisite or exclusion. Adequate but leaves routing to inference from the sibling names.

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