Skip to main content
Glama

Estimate Wedding Alcohol

zola_estimate_wedding_alcohol
Read-only

Zola's general estimate of how much alcohol to buy for a wedding bar: the total drinks, the bottles of wine, the 750 ml bottles of liquor, the cases of beer, and the champagne for a toast. It counts 1.5 drinks per guest who drinks in the first hour and 1 drink each hour after, multiplied by 0.75 for a crowd that drinks below average and 1.5 for a crowd that drinks above average. The pours are the standard US pours: 5 oz of wine, 1.5 oz of liquor, 12 oz of beer. The default mix is 50% wine, 30% liquor, and 20% beer. For a beer-and-wine bar, give a mix with 0% liquor. It gives no cost.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "guest_count": "<guest_count>",
      "hours": "<hours>"
    },
    "name": "zola_estimate_wedding_alcohol"
  }
}

Input Schema

NameRequiredDescriptionDefault
crowdNoHow much the guests drink. Default average
hoursYesHours of the bar, with the cocktail hour, in half hours, from 1 to 12
guest_countYesNumber of guests
mix_percentNoShare of the drinks for each type, in percent, that adds up to 100. Default 50% wine, 30% liquor, 20% beer
non_drinkersNoGuests in guest_count who will not drink alcohol, with the guests under 21. Default 0
champagne_toastNoAdd 1 glass of champagne per guest who drinks for the toast. Default false

Output Schema

NameRequiredDescriptionDefault
beerYesBeer
wineYesWine
crowdYesHow much the guests drink
hoursYesHours of the bar
liquorYesLiquor
sourcesYesThe Zola article, and the Moët page for a toast
assumptionsYesThe values that the estimate uses
guest_countYesNumber of guests
non_drinkersYesGuests who do not drink alcohol
total_drinksYesDrinks for the whole bar, rounded up. The toast is not in it
champagne_toastNoChampagne for the toast, only with champagne_toast
drinking_guestsYesGuests who drink: the bar and the toast are for them

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare a safe, closed-world read, so the description's job is to explain the calculation, and it does: 1.5 drinks per drinking guest in hour one, 1 per hour after, crowd multipliers of 0.75/1.5, standard US pours, default 50/30/20 mix, and an explicit 'gives no cost' limitation. What it does not disclose is anything about output shape or rounding, though an output schema exists to cover that.

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?

The first sentence front-loads the purpose and outputs, and each following sentence carries a distinct fact (drink formula, pours, default mix, beer-and-wine case, no cost). It is dense but not padded; only the mix restatement slightly overlaps the schema.

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 six-parameter estimator with a full output schema and read-only annotations, the description covers methodology, defaults, and the absence of cost output, which is what an agent needs to trust and present the result. Return-value details are correctly left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3; the description goes beyond by quantifying what the 'crowd' enum actually does (0.75x below average, 1.5x above average) and restating the pour sizes that make 'hours' and 'guest_count' meaningful. It adds real interpretation without duplicating the schema verbatim.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 ('estimate of how much alcohol to buy for a wedding bar') and immediately enumerates the outputs (total drinks, wine bottles, 750 ml liquor bottles, beer cases, champagne). It is unambiguously distinct from the sibling budget, timeline, and vendor tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It supplies a concrete usage rule for a common variant: 'For a beer-and-wine bar, give a mix with 0% liquor.' It does not name an alternative tool or state when not to use it, but no sibling appears to overlap, so the gap is small.

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