Skip to main content
Glama

Search the Zola Registry Shop

zola_search_registry_products
Read-only

Search the products of the Zola registry shop, for registry ideas or a gift: kitchen, home, travel, experiences, and more, with the price and the product page. Not for finding a couple's own registry.

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

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to find, with the type, brand, color, or style, for example 'cast iron dutch oven'
max_priceNoThe highest price in whole US dollars

Output Schema

NameRequiredDescriptionDefault
statusYesno_results when no product of the Zola registry shop matches
productsYesThe matching products of the Zola registry shop
search_urlNoThe zola.com shop search, when the products of the search are all above max_price

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/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 the safety profile is covered structurally. The description adds that results carry a price and a product page, but says nothing about result caps, ranking, or pagination behavior for a search tool.

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?

The verb and resource are front-loaded and there is no filler; the category list and exclusion both earn their place. It is a single long sentence with layered colons, which is dense but still readable and appropriately sized.

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?

With only two fully documented parameters and an output schema handling return values, the definition covers what an agent needs to invoke it correctly. The only gap is operational behavior of the search itself (result count, ordering), which is minor for this simple lookup.

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 both parameters already carry their own descriptions, including an example query and the whole-dollar price bound. The description's mention of 'price' loosely maps to max_price but adds no syntax or filtering semantics beyond the schema.

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 ('Search the products of the Zola registry shop') and enumerates the catalog categories (kitchen, home, travel, experiences). It also explicitly scopes out the adjacent capability of finding a couple's own registry, which distinguishes it from zola_find_couple.

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?

It states the two intended scenarios ('for registry ideas or a gift') and an explicit exclusion ('Not for finding a couple's own registry'). It stops short of naming the sibling tool that handles the excluded case, so the agent must infer the redirect rather than being routed directly.

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