Skip to main content
Glama

Search like a customer

storefront_search
Read-onlyIdempotent

Search a Shopware sales channel exactly as a customer to return Store API results with real visibility, stock, ranking, and prices; optionally explain a product's rank or absence.

Instructions

Run a search in a sales channel exactly as a customer would, through Shopware's Store API: same visibility, stock and closeout rules, same ranking and prices. Optionally explain one product: its position in the results, or why it does not show up (inactive, not visible in the channel, link-only visibility, closeout without stock, not in the search index, no search keyword matching the term). Read-only. Returns { salesChannel, term, total, items[], explain? }.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "term": "<term>"
    },
    "name": "storefront_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesWhat the customer types
limitNoResults to return
explainNoProduct number to explain: where it ranks, or why it is missing
salesChannelNoSales channel id or name; default: the first active storefront

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.1

TDQS

D1.4/5.0
Behavior1/5

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

No annotations are supplied and the description discloses nothing about side effects, permissions, idempotency, or return shape. With zero structured coverage, the description carries the full burden and delivers none of it.

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

Conciseness2/5

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

It is short, but only because it is under-specified rather than concise. There is no structure to speak of beyond a single bare word.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and no parameters documented, the description is the only source of information about this tool and it provides none. An agent cannot determine what the tool operates on or what it returns.

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?

The schema declares no parameters, so there is no coverage gap the description needs to fill and no argument semantics to clarify. However, the description adds no value whatsoever about what input, if any, the tool consumes, leaving this dimension neutral rather than strong.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Process" merely restates the tool name and title. It names no resource, no verb of substance, and gives no way to tell it apart from any of the ~37 sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no indication of when to call this tool, when not to, or which sibling to prefer instead. An agent has no basis for selecting it over products_search, orders_search, or entity_search.

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