Skip to main content
Glama

BRAINIAC Restaurant Operations Intelligence

Rank menu profitability

restaurant-operations_menu-profitability-rank
Read-onlyIdempotent

Rank menu items by contribution using calculated portion profit and supplied sales units. Ties fall back to gross margin. Price $0.05 USDC. POST /api/v1/restaurant-operations/menu-profitability-rank. 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-profitability-rank"
  }
}

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

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

Annotations already declare readOnly, idempotent, non-destructive, so the description correctly spends its words elsewhere: it discloses the $0.05 USDC cost, the POST transport, and — most usefully — that an unpaid call returns x402 payment terms and does not execute. That payment/auth behavior is not derivable from any structured field. It does not cover failure modes beyond non-payment, so it is not 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 purpose, then tie-break, then price and endpoint, then payment failure behavior. The raw POST path is low-value filler for an agent, but everything else earns its place.

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, deeply nested input the description gives purpose, cost, transport and payment semantics, and an output schema exists so return values need no explanation. What is missing is how the optional nested inputs interact to produce 'calculated portion profit' — whether the caller must supply recipes, recipe lines and prices together or whether sales alone suffices.

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% and each of the 13 parameters carries a description, so the baseline is 3. However those descriptions are mechanical ('sales, array. Optional.'), and the tool description only gestures at two of them ('supplied sales units', 'portion profit'); the relationships between recipes, recipeLines, ingredients and prices that drive the calculation are left unstated.

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 ('Rank menu items by contribution'), names the ranking metric (calculated portion profit) and the tie-break rule (gross margin), so the operation is unambiguous. It stops short of naming a sibling such as menu-item-margin-analyze, so an agent cannot tell purely from the text which of the cost/profit tools to pick.

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 implied rather than stated: the mention of 'calculated portion profit and supplied sales units' hints at required input data (recipes, recipe lines, prices, sales), but there is no explicit when-to-use, when-not-to-use, or named alternative among the six sibling analysis tools. An agent must infer the routing decision.

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