Skip to main content
Glama

List configured stores

list_stores
Read-only

List the Shopify stores this server is configured for and return each store's alias, which every other tool requires. Call it first to confirm store setup before syncing or comparing.

Instructions

List the Shopify stores this server is configured for. Call it first: the aliases it returns are the store names every other tool takes (source, target, store). Returns { server, stores: [{ alias, domain, label, apiVersion, auth, allowWrites, protected }] }. allowWrites=false means apply_plan refuses that store; protected=true means a person confirms every apply to it. An empty list means no store is set up yet. Tokens and secrets are never returned. Takes no arguments and makes no Shopify calls. Next: list_resource_types for what can be synced, diff_stores to compare two stores.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, yet the description adds real behavioral context: no Shopify calls are made, tokens and secrets are never returned, an empty list means no store is configured, allowWrites=false causes apply_plan to refuse the store, and protected=true requires human confirmation per apply. That cross-tool consequence disclosure goes well beyond the annotations.

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?

Front-loaded with purpose and the 'call it first' instruction, then a compact inline return shape, then field semantics, then edge cases, then next steps. Every sentence carries information an agent would otherwise have to guess, and the parenthetical field list keeps the return description to one line.

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?

There is no output schema, so the description carries the full burden of describing the response — and it does so precisely, enumerating server and each store field plus the meaning of the two boolean-ish fields. With zero params and annotations covering the safety profile, nothing an agent needs to invoke or interpret this tool 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?

The tool takes zero parameters, so the baseline is 4; the description confirms this explicitly ('Takes no arguments'), removing any ambiguity about hidden filtering options. The semantic detail it does supply concerns the return object rather than inputs, which does not raise it further.

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 the Shopify stores this server is configured for') and immediately establishes its unique role as the discovery tool whose aliases parameterize every other tool. An agent can distinguish it from diff_stores or list_resource_types without opening any 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?

Explicit sequencing guidance: 'Call it first' plus named next steps (list_resource_types for syncable resources, diff_stores for comparison). It also explains the downstream consequence of its output (aliases are the store names other tools take), which is exactly the routing information an agent needs.

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