Skip to main content
Glama

Get Wedding Tipping Guide

zola_get_tipping_guide
Read-only

Zola's general tipping guide: how much couples tip wedding vendors (caterer, hair and makeup, photographer, videographer, DJ or band, planner, drivers, officiant, florist, delivery and setup teams), from Zola's tipping guide and Zola's 2026 Wedding Spend Survey. With a vendor type and its service cost, also gives the tip range in US dollars.

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_get_tipping_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendor_typeNoVendor type. Omit for all vendor types.
service_costNoWhat the vendor costs, in US dollars. Only with vendor_type, for a vendor with a percent tip.

Output Schema

NameRequiredDescriptionDefault
sourceYesThe Zola article that gives these values
vendorsYesThe tips for each vendor type

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?

The annotations already establish a safe read-only lookup, so the description is not obliged to restate that. It adds genuine value beyond them by naming the data provenance (Zola's tipping guide and the 2026 Wedding Spend Survey) and by disclosing that the dollar range is computed only for percent-tip vendors. Return format and pagination are not discussed, but 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?

Two sentences, front-loaded with the resource and scope, followed by the optional compute behavior. The long parenthetical list of vendor types partially duplicates the enum, but it aids quick semantic matching on terms like 'officiant' or 'florist.' Little is wasted overall.

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?

With annotations, full schema coverage, and an output schema, the remaining burden is small: explain scope, source, and the conditional output. The description does all three. It could go slightly further by clarifying whether flat-fee vendors return guidance without service_cost, but nothing essential for correct invocation is missing.

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 both parameters are already well documented, including the enum and the 'Only with vendor_type' constraint. The description reinforces the pairing of vendor_type and service_cost and the percent-tip condition without adding syntax or format detail beyond the schema, which is the expected baseline.

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 uses a specific verb and resource: it returns Zola's tipping guide and states exactly how much couples tip vendors across ten named categories. An agent can tell this is a reference-data lookup rather than a calculator or a vendor search. It doesn't explicitly distinguish itself from nearby planning tools like the who-pays guide or the budget estimator, which keeps it below 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?

The second sentence conveys the key usage pattern: supply a vendor type plus its service cost to receive a dollar tip range. That is real guidance for the optional combination. However, there is no explicit statement of when to use this versus the who-pays or budget tools, and no exclusions beyond the schema's 'Omit for all vendor types.'

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