Synchronity

search_products

Read-only

Find products on a registered store. To BROWSE a store's catalog (open-ended requests like "what do they sell", "show me what's available"), call with NO query — this returns the store's products. To SEARCH, pass query (a product name/keyword). Returns paginated products as an interactive card. ALWAYS translate a buyer's budget or price constraint into the price params on THIS call instead of filtering in your reply: "under/below/within X" or "X budget" → max_price: X; "over/above/at least X" → min_price: X; "between X and Y" → both. Likewise pass in_stock: true for "available"/"in stock" and category when they name one. The card renders exactly what this call returns, so the filter MUST be applied here — never fetch the full catalog and then narrow it in text. Call once with your best intent (browse OR a single query); if a real search is genuinely empty, ask the user to clarify rather than re-firing reworded queries. The card shows products, prices, IDs, and Add-to-cart controls — keep your text reply to one brief sentence and do not re-list what the card shows.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (1-indexed, default: 1)
`query`	No	Optional single search term (product name/keyword). OMIT to browse; for several names use `queries`.
`queries`	No	Search several product names at once (e.g. when the buyer lists multiple items). Returns all matches in ONE call/card instead of searching one at a time. Use `query` for a single search, `queries` for several, or omit both to browse.
`site_id`	Yes	Registered site ID (e.g., "site_abc123" or "shopify_store_1")
`category`	No	Filter by product category (optional)
`in_stock`	No	Filter to in-stock items only (default: false)
`per_page`	No	Results per page (default: 20, max: 100)
`max_price`	No	Maximum price filter in store currency, format: "199.99" (optional)
`min_price`	No	Minimum price filter in store currency, format: "19.99" (optional)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	Yes
`siteId`	Yes
`products`	Yes
`siteName`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 21, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already indicate safe read (readOnlyHint=true) and open-world results (openWorldHint=true). Description adds detail: the card shows products, prices, IDs, and Add-to-cart controls, and emphasizes that filters must be applied via parameters. No contradiction.

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 description is lengthy but every sentence serves a purpose. It front-loads the main action and then systematically covers usage patterns. Could be slightly trimmed but remains well-organized and efficient for the complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists (not shown), the description fully covers usage, parameter mapping, and behavioral expectations. Includes edge cases like empty results and multiple queries. No gaps for the complex 9-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3). Description significantly adds value by explaining the browse vs search distinction for query/queries, and provides concrete examples for mapping user phrases to price params and in_stock/category. Goes well beyond schema descriptions.

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?

Clearly states it finds products on a registered store, distinguishes between browsing (no query) and searching (with query), and mentions the interactive card result. Differentiates from sibling tools like get_product and compare_products.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Provides explicit guidance on when to browse vs search, instructs to map buyer budget/price constraints to parameters, advises calling once with best intent, and handles empty results. Also tells the agent to keep replies brief and not re-list the card.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Synchronity tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.