Skip to main content
Glama

Get Who Pays Guide for the Wedding

zola_get_who_pays_guide
Read-only

Zola's general guide to who traditionally pays for each wedding cost (the bride's parents, the groom's parents, the couple, the wedding party, or the guests), and how couples pay for their wedding today, from Zola's guide. It gives no percentages.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
factsYesHow couples pay for their wedding today
itemsYesWedding costs and who traditionally pays for each
sourceYesThe Zola article that gives these values

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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=false, so safety is covered. The description adds genuinely useful behavioral context beyond that: the answer is qualitative and categorical, with no numerical percentages, which prevents an agent from promising cost figures. It doesn't describe format, but an output schema exists to carry 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?

A single front-loaded sentence that lists the payer categories directly and ends with the most decision-relevant caveat. Minor redundancy in restating 'Zola's guide ... from Zola's guide,' but no sentence is wasted.

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 zero-parameter, read-only content lookup with an output schema and full annotation coverage, the description supplies everything needed: subject matter, scope of categories, and the absence of percentages. Nothing material is missing for correct invocation.

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?

The tool takes no parameters, so the baseline is 4 and the schema requires no semantic explanation. Nothing in the description is needed to call it correctly.

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 who-pays guide) and enumerates exactly what it covers: the traditional payer categories (bride's parents, groom's parents, couple, wedding party, guests) plus modern payment practices. It does not name a sibling alternative, but the closing note that it 'gives no percentages' implicitly separates it from the budget/estimate tools.

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 implied by the content description rather than stated — an agent can infer this is the lookup for etiquette questions about who covers a cost, but there is no explicit 'use when' phrasing or named alternative. The 'no percentages' caveat weakly steers toward the estimator siblings without saying so.

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