Skip to main content
Glama

Estimate Wedding Budget

zola_estimate_wedding_budget
Read-only

Use this when the user asks how much a wedding costs in general, or how to split a budget. Zola's general estimate of the total cost of a wedding in a US city, state, or wedding market, and the typical cost of each budget category (venue, catering, photographer, and more), from Zola data. Not for finding vendors. Do not use for the couple's own budget, costs or payments: use zola_get_my_budget.

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": "zola_estimate_wedding_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationNoCity and state (for example 'Chicago, IL'), a state ('Texas'), or a wedding market ('Long Island'). Omit for a United States estimate.
guest_countNoNumber of guests. Omit when the user did not say.
total_budgetNoThe couple's own total budget, in whole US dollars, from 1,000 to 10,000,000. When given, the categories split this total.

Output Schema

NameRequiredDescriptionDefault
totalNoEstimated total wedding cost
statusYesestimate: the estimate is in this result. ambiguous_location: more than one place matches. location_not_found: Zola does not know the place.
categoriesNoTypical cost of each budget category
guest_countNoGuest count of the estimate
guest_count_noteNoWhy the guest count of the estimate is not the requested count
estimate_locationNoThe place that the estimate is for. It can be the state or the country when Zola has no data for the requested place.
requested_locationNoThe place name that was asked for
total_budget_centsNoThe couple's own total budget, in cents. When present, the categories split this total.
location_candidatesNoThe places that match the requested name, when there is more than one

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds meaningful context beyond them: the figures are Zola-sourced general market estimates rather than the couple's data, and the tool is not a vendor lookup. Return shape is left to the output schema, which exists.

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?

Three sentences, front-loaded with the trigger and the exclusion, with no filler or marketing language. Slight redundancy between 'how to split a budget' in the usage clause and the total_budget behavior, but nothing that wastes the reader's attention.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 the three optional parameters are fully specified in the schema. The description covers data provenance, scope, and the sibling boundary, which is everything an agent needs to call this correctly.

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 'location', 'guest_count' and 'total_budget' are already fully documented with examples and ranges in the schema. The description adds only a light framing of location granularity (city, state, or wedding market) that the schema already conveys. Baseline 3 applies since the schema does the heavy lifting.

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?

States a specific verb and resource ('Zola's general estimate of the total cost of a wedding... and the typical cost of each budget category') and explicitly excludes two neighbors: vendor search and the couple's own budget. An agent can select this over zola_get_my_budget or zola_search_vendors without opening any schema.

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

Usage Guidelines5/5

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

Opens with an explicit trigger ('when the user asks how much a wedding costs in general, or how to split a budget') and names the contrasting case plus the exact alternative to use ('Do not use for the couple's own budget, costs or payments: use zola_get_my_budget'). Both the when and the when-not are present with a named redirect.

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