UCP Checker & Router

Search Policies

search-policies

Read-only

Search store policies on any UCP-enabled Shopify store.

Query return policies, shipping policies, refund policies, privacy policies,
terms of service, or any other store policy. Returns the matching policy text.

Use this when a user asks about a store's policies before or after purchase —
e.g., "what is the return policy?", "do they offer free shipping?", "refund window?"

Example: domain: "allbirds.com", query: "return policy"

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Policy search term (e.g., "return policy", "shipping", "refund window", "privacy policy")
`domain`	Yes	The store domain (e.g., "allbirds.com")

TDQS

A4/5.0

Behavior3/5

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

Description discloses that it searches policies and returns the matching text, and notes the UCP-enabled store constraint. This adds context beyond the readOnlyHint annotation, which only declares the operation is read-only. It doesn't cover error cases or limitations, but the added scope is useful.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four concise sentences. The first sentence states the purpose, subsequent sentences provide usage guidance and an example. No redundancy; every sentence earns its place.

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 simple 2-parameter tool, the description covers what it does, when to use it, expected inputs (via schema), and the return behavior (matching policy text). The UCP constraint is also stated. It doesn't specify output formatting, but the description's 'Returns the matching policy text' is sufficient given no output schema.

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%, with both 'domain' and 'query' already documented. The description reinforces with examples (allbirds.com, 'return policy') but adds no new parameter meaning. Baseline 3 is appropriate given the schema carries the semantic load.

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?

States a specific verb (Search) and resource (store policies) with an explicit scope ('any UCP-enabled Shopify store'). Lists policy types and clarifies the return value ('Returns the matching policy text'). This clearly distinguishes it from siblings like search-catalog or get-product-details.

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 explicit usage context: 'Use this when a user asks about a store's policies before or after purchase' with concrete examples (e.g., 'what is the return policy?'). Does not mention alternatives, but the context is clear enough for an agent to decide when to invoke it.

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?