Skip to main content
Glama

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 profile, 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list-stores"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of stores to return (default and max: 10)
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. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of stores to return (default: 10, max: 50)"New value: +"Maximum number of stores to return (default and max: 10)"
  2. 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"
      -}
  3. Changed1 schema field changed
    • addedInput schema / properties / platform
      Added value: +{
      +  "description": "Restrict to one platform, e.g. \"wix\", \"shopify\", \"woocommerce\".",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description adds substantial context beyond that. It defines the four evidence tiers (transactable, catalogued, resolvable, declared), explains that entries reflect observed rather than claimed state, and discloses scoping exclusions for previews and staging hosts — all of which change how results should be interpreted.

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 purpose and the sibling routing appear in the first two sentences, and the remaining content is a compact, bulleted glossary of evidence tiers plus two filter notes. No sentence is redundant with the schema or annotations.

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 must explain what returned records mean, and it does so via the tier definitions and the "observed, not claimed" framing. Combined with the filter guidance and exclusion notes, an agent has everything needed to call the tool and interpret its results 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: `category` is scoped to deeply audited stores and should usually be omitted, and `platform` is illustrated with concrete values (shopify, wix, woocommerce, bigcommerce, shopware). It does not restate `limit`, but that is already fully documented in the schema.

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 ("List verified UCP storefronts across every platform") and states the ordering rule ("best-evidenced first"). It is clearly distinguished from search-all and list-categories, so an agent can pick it without opening sibling schemas.

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?

It gives explicit when-to-use phrasing with concrete user utterances ("what stores can I shop at?", "show me Wix stores") and names the alternative for a related intent ("To find stores that sell something, prefer search-all"). It also tells the agent to leave `category` out unless requested and warns that developer previews and staging hosts are excluded.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources