UCP Checker & Router

Search Catalog

search-catalog

Read-only

Search for products on any UCP-enabled Shopify store.

Searches the store's live product catalog via UCP/MCP and returns
matching products with titles, prices, variants, and images.

Examples:
- domain: "allbirds.com", query: "tree topper"
- domain: "gymshark.com", query: "hoodie"

Input Schema

TableJSON Schema

Name	Required	Description
`query`	Yes	Product search term (e.g., "tree topper", "wool runners", "hoodie")
`domain`	Yes	The store domain (e.g., "allbirds.com", "gymshark.com"). Must be a UCP-enabled Shopify store.
`country`	No	ISO country code for localized pricing/inventory (e.g., "US", "GB", "CA"). Optional — defaults to store default.

TDQS

A3.7/5.0

Behavior4/5

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

readOnlyHint=true is consistent with a search operation. The description adds useful behavioral context: it searches the store's live product catalog, returns specific fields, and supports localized pricing/inventory via country. It does not cover pagination or rate limits, but for a read-only search tool the essentials are present.

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 efficiently organized: a clear one-line summary, a short elaboration on return content and behavior, then concrete examples. Each section earns its place, and there is no significant fluff.

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 no output schema, the description adequately compensates by listing returned product attributes. It specifies required parameters via examples and the schema covers the optional country. Potential error cases or result pagination are not mentioned, but for this tool's scope the essentials are covered.

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 description coverage is 100%, so all parameters (query, domain, country) are already documented in the schema. The description's examples reinforce value formats and the country parameter's default, but it adds little beyond what the schema supplies.

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?

The description clearly states 'Search for products on any UCP-enabled Shopify store' and details what is returned (titles, prices, variants, images). It does not explicitly distinguish itself from siblings like search-all, but the required domain parameter and the phrase 'any ... Shopify store' make the per-store scope evident.

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

Usage Guidelines3/5

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

Usage context is implied by the domain and query examples, but there is no explicit when-to-use or when-not-to-use guidance, nor are alternative tools like search-all or get-product-details mentioned. An agent can infer this is for per-store searches, but it isn't told.

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

All UCP Checker & Router tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct resource or action: domain status, store capabilities, product variants, categories, store listings, aggregate search, single-store search, and policies. The only similar pair, search-all and search-catalog, is clearly differentiated by scope in their descriptions.

Naming Consistency5/5

All tool names follow the same lowercase hyphenated verb_noun pattern, such as check-domain, list-stores, and search-catalog. Verbs are consistently placed first and accurately describe each action.

Tool Count5/5

Eight tools is well within the ideal range, and each tool serves a distinct step in the UCP discovery and shopping workflow. There are no redundant or extraneous tools.

Completeness4/5

The set covers UCP checking, store and category discovery, single-store and multi-store product search, product details, and policy lookup. Direct cart or checkout operations are absent, but discover-store can reveal such capabilities, making the core discovery workflow reasonably complete.

Resources

Need Help?