Skip to main content
Glama

UCP Checker & Router

by com.ucpchecker

Search All

search-all
Read-only
Search for products across the highest-scoring verified UCP stores at once.

Fans out the query to multiple stores concurrently and returns
aggregated results grouped by store. Stores are chosen from the same
vetted, scored set list-stores returns (best scores first). Pass
`category` to focus the fan-out — e.g. "footwear" for "running shoes".
Slow/failing stores are skipped gracefully.

Example: query: "running shoes", category: "footwear", maxStores: 5

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesProduct search term (e.g., "running shoes", "hoodie")
countryNoISO country code for localized pricing (e.g., "US", "GB"). Optional.
categoryNoLimit the fan-out to one store category (e.g., "footwear"). Use list-categories to see available categories. Optional but recommended for focused queries.
maxStoresNoMaximum number of stores to search (default: 5, max: 10)

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses meaningful behavior: concurrent fan-out, results grouped by store, selection from the scored `list-stores` set, and graceful skipping of slow/failing stores. This gives the agent a realistic picture of execution semantics.

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?

The description is front-loaded with the core purpose and packs useful behavioral and usage detail into a compact format. The example is relevant and reinforces the parameter semantics without adding fluff.

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?

For a read-only search tool with no output schema, the description explains what is searched, how stores are selected, how results are grouped, what happens on failures, and how to narrow the query. Nothing essential is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value by explaining that `category` limits fan-out and by giving a concrete example ('running shoes', 'footwear', maxStores: 5), which clarifies how parameters interact.

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 opens with a specific verb and resource: 'Search for products across the highest-scoring verified UCP stores at once.' It clearly differentiates itself from single-store or catalog-specific siblings by emphasizing concurrent fan-out across multiple stores.

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?

The description clearly conveys when this tool is appropriate: for multi-store product search across the vetted store set. It advises using `category` to focus the fan-out and references `list-categories` via the schema, but it does not explicitly say when to prefer `search-catalog` or other siblings instead.

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 toolsInspect
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