Skip to main content
Glama

BRAINIAC Restaurant Operations Intelligence

Validate allergen matrix

restaurant-operations_allergen-matrix-validate
Read-onlyIdempotent

Compare menu allergen claims with explicitly supplied ingredient allergen flags. Allergen status is never invented and food-safety compliance is not claimed. Price $0.05 USDC. POST /api/v1/restaurant-operations/allergen-matrix-validate. 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_allergen-matrix-validate"
  }
}

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.
mismatchCountNomismatchCount. Number.
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?

Adds substantial behavior beyond the annotations: it will not invent allergen status, does not assert food-safety compliance, costs $0.05 USDC, uses POST /api/v1/restaurant-operations/allergen-matrix-validate, and an unpaid call returns x402 payment terms without running. The payment-gate behavior is the kind of operational detail annotations cannot convey.

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?

Five short sentences, front-loaded with purpose and the no-invention guarantee. The endpoint path and price are procedural but earn their place for an agent that must handle the payment flow.

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?

Given an output schema exists and the schema fully describes parameters, the description covers purpose, truth-sourcing limits, cost, and the unpaid-call failure mode. It could say more about which inputs drive the comparison and what happens on missing data.

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 baseline is 3. The description maps conceptually to the two key arrays (matrix claims and ingredient allergen flags) but adds no format, pairing, or required-input semantics for the 13 nested parameters.

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 ('Compare menu allergen claims with explicitly supplied ingredient allergen flags'), which is clearly distinct from the cost/margin siblings. It doesn't explicitly name or contrast with an alternative tool, so it stops short of a 5.

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?

Implies usage through the constraint that allergen flags must be 'explicitly supplied', which tells the agent the caller must provide source data. There is no explicit when-to-use or when-not-to-use guidance relative to the sibling analysis tools.

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