Skip to main content
Glama

Find a Couple on Zola

zola_find_couple
Read-only

Find the Zola wedding website and registry of one couple, for a guest who knows the couple. Give the first and last name of one partner, and the name of the other partner or the year and month of the wedding. Gives the links of one couple only, from the couples who let guests find them on zola.com. When no single couple matches, gives the zola.com couple search.

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": {
      "first_partner": "<first_partner>"
    },
    "name": "zola_find_couple"
  }
}

Input Schema

NameRequiredDescriptionDefault
first_partnerYesThe first and last name of one partner
wedding_monthNoThe year and month of the wedding, YYYY-MM, for example 2027-06. Necessary when second_partner is not given
second_partnerNoThe name of the other partner

Output Schema

NameRequiredDescriptionDefault
statusYesfound: one couple with the names given. found_close_names: one couple with names that are near the names given, which the user must make sure of. not_found: no single couple matches, so use search_url
search_urlNoWith not_found: the zola.com couple search for the names given
website_urlNoThe couple's Zola wedding website
registry_urlNoThe couple's Zola registry
names_on_zolaNoWith found_close_names only: the Zola spelling of the names that the user gave
wedding_monthNoThe month of the wedding, for example 'June 2027'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already mark this as a safe, non-destructive read with a closed world, so the description doesn't need to restate that. Instead it adds real context beyond the annotations: results are limited to couples who opted into being findable, only one couple's links are returned, and a fallback search is provided when matching fails. What's missing is anything about ambiguity or multiple partial matches beyond the fallback sentence.

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?

At four sentences it stays front-loaded, leading with the outcome, then the inputs, then the scope, and then the fallback. The phrasing is slightly repetitive, for example 'Find... one couple' followed by 'Gives the links of one couple only', so it could be tightened, but nothing 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?

The tool's complexity is low, it has only three flat parameters, and an output schema exists, so the description doesn't need to explain return shapes. It covers scope, inputs, and the no-match path, which is enough for an agent to call it correctly. The only gap is how ties or multiple partial matches other than the full fallback are handled.

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%, and the schema already documents each parameter, including that wedding_month is necessary when second_partner is not given. The description restates that either/or requirement in prose, which is actionable but largely redundant with the structured fields. The baseline of 3 for full schema coverage applies.

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 names a specific verb and resource: it finds the Zola wedding website and registry of one couple. It also scopes the result to one couple only, which makes it clearly distinct from the sibling search tools that cover advice, vendors, invitations and registry products.

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?

The description states the intended caller ('a guest who knows the couple') and the input combinations required to call the tool. It also describes the failure path: when no single couple matches, it returns the zola.com couple search. It doesn't list explicit when-not-to-use cases, but the audience restriction covers most of that.

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