Skip to main content
Glama

Suggest a Wedding Gift Amount from Zola's Guide

zola_suggest_cash_gift_amount
Read-only

Zola's general guideline for how much a guest spends on a wedding gift, in cash or from the registry, for the guest's relationship to the couple, and the average wedding gift from Zola's 2026 First Look Report.

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": {
      "relationship": "<relationship>"
    },
    "name": "zola_suggest_cash_gift_amount"
  }
}

Input Schema

NameRequiredDescriptionDefault
relationshipYesThe guest's relationship to the couple

Output Schema

NameRequiredDescriptionDefault
sourceYesThe Zola article that gives these values
low_usdYesLow end of Zola's guideline, in US dollars
high_usdYesHigh end of Zola's guideline, in US dollars
most_guestsYesWhat most guests spend, from Zola's 2026 First Look Report
relationshipYesThe guest's relationship to the couple
open_ended_highYesTrue when the guideline is high_usd or more
average_gift_usdYesAverage wedding gift in Zola's 2026 First Look Report, in US dollars

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With annotations already declaring readOnlyHint, openWorldHint=false and destructiveHint=false, the safety profile is covered. The description does add useful context, namely that the output is a general guideline (not a personalized quote) and comes from a dated 2026 report, but it says nothing about range vs. single figure, currency, or regional assumptions.

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?

A single front-loaded sentence with no filler; every clause names a distinct part of the output. The phrasing 'for the guest's relationship to the couple' is slightly convoluted but earns its place by tying the parameter to the result.

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 one-parameter read-only lookup with an output schema and full annotation coverage, the description supplies enough: what it returns, the basis for the numbers, and the input dimension. Only the currency/region scope and range-vs-point-estimate questions remain open, which is a minor gap.

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% with a fully enumerated relationship field, so the schema carries the parameter documentation. The description adds meaning by tying the relationship input to the gift amount outcome and noting the amount applies whether given in cash or via the registry.

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 names a specific resource (Zola's wedding gift amount guideline) and the two dimensions it covers: amount by guest-to-couple relationship and the 2026 First Look Report average. That distinguishes it from guide siblings like zola_get_tipping_guide and zola_get_who_pays_guide, though it never names an alternative explicitly.

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 only implied: an agent can infer this is for answering 'how much should I give' questions, but the description never states when to use it, when not to, or which sibling guide to pick instead. There is no exclusion or prerequisite guidance.

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