Skip to main content
Glama

BRAINIAC Restaurant Operations Intelligence

Detect ingredient price variance

restaurant-operations_ingredient-price-variance
Read-onlyIdempotent

Compare supplied supplier prices for the same ingredient after unit conversion and report spreads and dated changes. Prices are never invented. Price $0.04 USDC. POST /api/v1/restaurant-operations/ingredient-price-variance. 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_ingredient-price-variance"
  }
}

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?

The annotations already establish read-only, idempotent, non-destructive behavior, so the bar is lower; the description adds genuinely non-inferable traits: a fixed price of $0.04 USDC, the POST endpoint, and the x402 flow where an unpaid call returns payment terms without executing. It does not describe rate limits or what the report payload looks like, but the payment/execution semantics are the important disclosure here.

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 with the core purpose front-loaded, followed by provenance, price, endpoint, and payment behavior in descending priority. No filler; only the raw endpoint path is arguably redundant padding.

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?

With 13 optional parameters, nested objects, and multiple alternative input representations, the description does far less than it could — it never says whether to use csv, json, text, or file, nor which companion datasets (ingredients, recipes, recipeLines) are needed for the variance math. It does, however, explain the payment gate and the fact that an output schema exists relieves it of return-value detail.

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 of 3 applies, but the schema descriptions are pure boilerplate ('csv, string, length 0 to 200000. Optional.') with no domain meaning. The description only hints that a 'prices' collection with units drives the comparison; the five alternative input channels (csv, json, text, file, sales/waste/matrix/recipes side data) are never explained.

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 opens with a specific verb and resource: 'Compare supplied supplier prices for the same ingredient after unit conversion', and it names the output ('spreads and dated changes'). That is enough to separate it from cost/recipe siblings, though it never names an alternative tool 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?

It implies usage conditions — you must supply the prices yourself ('supplied supplier prices', 'Prices are never invented') and that comparison happens after unit conversion. There is no explicit when-not guidance and no routing to sibling tools such as recipe-cost-calculate or food-cost-report, leaving the agent to infer selection.

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