Skip to main content
Glama

UCP Checker

by com.ucpchecker
OverviewDiscussionsAdmin

List Stores

list-stores
Read-only
List verified UCP storefronts across every platform, best-evidenced first.

Use when the user wants to browse stores — e.g., "what stores can I shop
at?" or "show me Wix stores". To find stores that sell something, prefer
search-all.

Each store carries what we have actually observed about it, not what it claims:

- `transactable` — declares checkout and we have read its catalogue
- `catalogued` — we have read its catalogue
- `resolvable` — its endpoint resolves, we have not probed it yet
- `declared` — a valid manifest, nothing observed beyond it

Filter by `platform` (shopify, wix, woocommerce, bigcommerce, shopware…).
`category` narrows to the smaller set of deeply audited stores (see
list-categories), so leave it out unless the user asks for a category.
Developer previews and staging hosts are not listed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of stores to return (default: 10, max: 50)
categoryNoOptional. Limit to the deeply audited stores in one category (e.g., "footwear"); see list-categories. Most browsing is better without it.
platformNoRestrict to one platform, e.g. "wix", "shopify", "woocommerce".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Filter by store category (e.g., \"footwear\", \"pet supplies\"). Use list-categories to see available categories."New value: +"Optional. Limit to the deeply audited stores in one category (e.g., \"footwear\"); see list-categories. Most browsing is better without it."
    • removedInput schema / properties / min_score
      Removed value: -{
-  "description": "Minimum total score to include (default: 50). Lower values return more stores but may include lower-quality ones.",
-  "type": "integer"
-}
  2. Changed1 schema field changed
    • addedInput schema / properties / platform
      Added value: +{
+  "description": "Restrict to one platform, e.g. \"wix\", \"shopify\", \"woocommerce\".",
+  "type": "string"
+}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, but the description goes well beyond that: it defines the evidence taxonomy (transactable/catalogued/resolvable/declared), explains the default ordering ('best-evidenced first'), and discloses an exclusion rule ('developer previews and staging hosts are not listed'). This is exactly the behavioral context the low-bar annotation set does not cover.

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?

Front-loaded with the core statement, then usage guidance, then the evidence taxonomy, then filters — a logical progression. The four-item taxonomy list is slightly verbose for a description, but each line carries distinct information the agent cannot get elsewhere.

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?

With no output schema, the description compensates by explaining what a returned store actually carries via the four evidence states. Combined with the filter semantics and explicit exclusions, there is nothing substantive an agent still needs in order to call this correctly.

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, but the description adds real meaning: it enumerates plausible platform values (shopify, wix, woocommerce, bigcommerce, shopware) and warns that category restricts to a smaller deeply-audited set that should usually be omitted. That is more than restating the schema's own text.

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 and resource ('List verified UCP storefronts') plus a scope modifier ('across every platform, best-evidenced first'). It distinguishes itself from siblings by name, explicitly contrasting with search-all and referencing list-categories, so an agent can route without opening either schema.

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?

Gives a concrete trigger ('when the user wants to browse stores') with two sample utterances, then names the alternative and its selecting condition ('To find stores that sell something, prefer search-all'). It also advises on optional narrowing ('leave it out unless the user asks for a category').

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

All UCP Checker toolsInspect
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.

Resources