Skip to main content
Glama

BRAINIAC Restaurant Operations Intelligence

Analyze menu item margins

restaurant-operations_menu-item-margin-analyze
Read-onlyIdempotent

Calculate gross margin and food-cost percentage from supplied sell prices and calculated recipe costs. Nutritional values are not invented. Price $0.05 USDC. POST /api/v1/restaurant-operations/menu-item-margin-analyze. 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_menu-item-margin-analyze"
  }
}

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.6/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely non-obvious behavior: a $0.05 USDC charge, an explicit POST endpoint, and the exact consequence of an unpaid call (terms returned, analysis not run). 'Nutritional values are not invented' also discloses an output-integrity constraint. It doesn't describe pagination or partial-input handling, which keeps it below a 5.

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?

Four short sentences, front-loaded with the purpose, then constraints, then cost and endpoint. Nothing is redundant; the 'Nutritional values are not invented' line is slightly oblique but carries real meaning.

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?

An output schema exists, so return values need no explanation, and payment mechanics are covered. The gap is input sufficiency: with 13 optional parameters and zero required, the description never explains which combination yields a valid analysis, which is the main thing an agent could get wrong here.

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 100%, so the baseline is 3. The description signals that sell prices and recipe costs are the operative inputs, but says nothing about the roles of sales, waste, prices, allergens, matrix, or the free-form csv/json/text/file carriers, all of which have to be learned from the schema alone.

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 (calculate) and specific outputs (gross margin, food-cost percentage) plus the inputs they derive from (sell prices, recipe costs). That distinguishes it reasonably well from siblings like recipe-cost-calculate or food-cost-report, though it never names an alternative explicitly.

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 mention of 'calculated recipe costs' hints this runs downstream of recipe costing, but there is no explicit when-to-use or when-not guidance relative to profitability-rank or food-cost-report. The caller is left to infer the sequencing.

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