Skip to main content
Glama

Search Zola Wedding Advice

zola_search_wedding_advice
Read-only

Search the Zola expert advice articles for wedding planning and etiquette: dress codes, invitation wording, traditions, ceremony and reception ideas, and how-to guides. Each result links its Zola article. Not for questions about Zola's own products and orders.

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": {
      "query": "<query>"
    },
    "name": "zola_search_wedding_advice"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe wedding planning topic or question, for example 'what does black tie optional mean'

Output Schema

NameRequiredDescriptionDefault
statusYesno_results when no Zola article matches
resultsYesThe best Zola expert advice articles, best first

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?

The annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds one useful behavioral note — 'Each result links its Zola article' — but says nothing about result ranking, count, or empty-result behavior; with an output schema present, that omission is tolerable.

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?

Three short sentences, front-loaded with the core action and scoped by the exclusion at the end. The topic enumeration is slightly long but directly useful for query formulation; no filler wording.

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?

A simple single-parameter read tool with full schema documentation, annotations covering safety, and an output schema handling return values — the description covers what remains (scope, topic coverage, exclusion). The only gap is not naming the help-articles sibling, which is a minor routing ambiguity.

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 single parameter already carries a description with a concrete example ('what does black tie optional mean'), so the schema does the heavy lifting. The description's topic list loosely mirrors what a good query looks like but adds no syntax, length, or phrasing guidance beyond the schema.

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 and resource ('Search the Zola expert advice articles') and enumerates the covered topics (dress codes, invitation wording, traditions, ceremony/reception ideas, how-to guides), so the agent knows exactly what corpus is searched. It stops short of naming the closest sibling, zola_search_help_articles, so the boundary is implied rather than explicit.

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?

Provides a clear negative boundary: 'Not for questions about Zola's own products and orders,' which steers product/order queries elsewhere. It gives no explicit positive trigger or named alternative, so the agent must infer which sibling handles the excluded cases.

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