Skip to main content
Glama

BRAINIAC Restaurant Operations Intelligence

Report restaurant food cost

restaurant-operations_food-cost-report
Read-onlyIdempotent

Combine recipe costs, margins, price variance, waste estimates, yield normalization, profitability ranking, and allergen validation from supplied data. Price $0.12 USDC. POST /api/v1/restaurant-operations/food-cost-report. 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-cost-report"
  }
}

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
wasteNowaste. Array.
statusNostatus. String.
yieldsNoyields. Array.
marginsNomargins. Array.
rankingNoranking. Array.
recipesNorecipes. Array.
findingsNofindings. Array.
allergensNoallergens. Array.
checkedAtNocheckedAt. String.
wasteCostNowasteCost. Number.
limitationsNolimitations. Array.
recipeCountNorecipeCount. Number.
priceInventedNopriceInvented. Boolean.
priceVarianceNopriceVariance. Array.
allergenInventedNoallergenInvented. Boolean.
nutritionInventedNonutritionInvented. Boolean.
pricedRecipeCountNopricedRecipeCount. Number.
wasteCostSuppliedNowasteCostSupplied. Boolean.
allergenMismatchCountNoallergenMismatchCount. Number.
foodSafetyComplianceClaimedNofoodSafetyComplianceClaimed. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), the description discloses two genuinely useful traits: a fixed cost of $0.12 USDC and the fact that an unpaid invocation returns x402 payment terms without executing. That payment-gating behavior is exactly the kind of context annotations cannot carry. It does not describe output shape or computation caveats, but the output schema covers returns.

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?

Three sentences: capability, price plus endpoint, then the payment-failure caveat. It is front-loaded with what the tool does and every sentence carries information. The only soft spot is that the analysis enumeration is dense, but it is doing real work in defining scope.

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?

The output schema exists, so return values need not be explained. However, with 13 parameters and zero required fields, the description gives no minimum viable input set or indication of which data blocks are needed for which analyses, leaving an agent unable to judge what to supply. For a compute-heavy paid endpoint, that is a meaningful completeness gap.

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 schema already documents all 13 parameters, and the baseline of 3 applies. The description's phrase 'from supplied data' and the list of analysis types loosely map to parameter groups (recipes/recipeLines, prices, waste, sales, matrix/allergens), but it adds no syntax, format, or unit guidance beyond the schema. It neither compensates nor detracts.

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 uses a specific verb ('Combine') and enumerates the concrete analyses produced: recipe costs, margins, price variance, waste estimates, yield normalization, profitability ranking, allergen validation. That makes the tool's role as a composite aggregate report unambiguous. It stops short of explicitly contrasting itself with the individual sibling endpoints, so it is clear but not sibling-differentiated.

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 enumeration of analyses suggests this is the all-in-one endpoint standing in for the granular siblings, but the description never says 'use this instead of calling the individual tools' nor states prerequisites or data minimums. The only explicit conditional is the payment case ('unpaid call returns x402 payment terms and does not run'), which is billing behavior rather than when-to-use guidance. An agent must infer the alternative-selection rule.

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