Skip to main content
Glama

BRAINIAC Restaurant Operations Intelligence

Estimate food waste cost

restaurant-operations_food-waste-estimate
Read-onlyIdempotent

Estimate waste cost from supplied waste quantities and ingredient prices after unit conversion. Missing prices are not invented. Price $0.04 USDC. POST /api/v1/restaurant-operations/food-waste-estimate. 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_food-waste-estimate"
  }
}

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.
totalEstimatedCostNototalEstimatedCost. Number.
totalEstimatedCostSuppliedNototalEstimatedCostSupplied. Boolean.
foodSafetyComplianceClaimedNofoodSafetyComplianceClaimed. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (which only cover read-only/idempotent/non-destructive semantics), the description discloses the payment model, the exact price ($0.04 USDC), the HTTP endpoint, and the critical gating behavior that an unpaid call returns x402 payment terms without executing. It also states that missing prices are not fabricated, which materially affects how results should be interpreted.

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?

Four short sentences, front-loaded with what it computes and its input basis, followed by the behavioral caveat and the payment/transport facts. No filler and no repetition of schema content.

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 13-parameter tool with an output schema, the description covers the essentials an agent needs before calling: the calculation basis, the no-fabrication rule, the cost, and the payment handshake. The remaining gap is that all 13 parameters are optional, so it is still left ambiguous which subset actually drives a valid estimate.

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 coverage is nominally 100%, so the baseline applies, but the schema itself only restates names and types. The description usefully ties the calculation to the waste quantities and price inputs and warns about absent prices, yet it adds no detail on asOf, unit conventions, or how records are joined (e.g. ingredientId matching).

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+resource ('Estimate waste cost') and names the determining inputs ('supplied waste quantities and ingredient prices') plus a processing trait ('after unit conversion'). It is clearly not a cost report or recipe-cost tool, though it never names a sibling to sharpen the boundary.

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: the agent can infer it should call this when it has waste entries and prices and wants a waste-cost figure. There is no explicit when-to-use versus restaurant-operations_food-cost-report or ingredient-price-variance, and no stated prerequisites for what input set is minimally required.

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