Skip to main content
Glama

Get Zola Customer Support Options

zola_get_support_options
Read-only

Get the contact details for Zola customer support: email, phone number, support hours, and the Zola Help Center, plus the contacts for wedding vendors, product vendors, and the press. Use when the user asks how to contact Zola, or needs a person to solve a problem with an order, a payment, or a Zola account.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
emailYesZola customer support email address
hoursYesWhen customer support answers email and phone, in US Eastern Time (IANA time zone America/New_York)
phoneYesZola customer support phone number, in the US, with the country code
other_contactsYesContacts for vendors and the press. Couples and guests use email and phone
help_center_urlYesZola Help Center with answers to common questions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 value by specifying the returned content categories (email, phone, hours, Help Center, vendor/press contacts), which tells the agent what a caller actually gets; it omits any note about data freshness or completeness, but nothing contradicts the annotations.

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 payload and followed by the trigger condition, with no filler. The return-value enumeration is slightly list-like but each item carries information an agent can relay to the user.

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 lookup with annotations and an output schema present, the description covers purpose, trigger, and returned content, which is sufficient to call it correctly. The one omission is guidance toward the article-search sibling when the user would be better served by self-service documentation.

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 zero parameters, so the schema baseline of 4 applies; there is no per-parameter meaning that needs explanation. The description correctly implies no targeting or filtering is required.

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?

States a specific verb ('Get') and resource ('contact details for Zola customer support') and enumerates exactly what is returned: email, phone, support hours, Help Center, vendor and press contacts. That enumeration makes it implicitly distinguishable from search_help_articles, but no sibling is named, so it stops short of 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 Guidelines4/5

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

Gives a clear trigger condition: 'Use when the user asks how to contact Zola, or needs a person to solve a problem with an order, a payment, or a Zola account.' It does not state when NOT to use it or point to the self-service alternative (search_help_articles) when a human contact is unnecessary.

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