shopware-mcp

Why are orders not coming in?

shop_diagnose

Read-only

Diagnoses Shopware issues when orders stop or customers complain by checking maintenance, test checkout, recent extensions, log errors, and stalled tasks, returning likely causes and verified checks.

Instructions

Look at the usual suspects in one call when orders stop or customers complain: storefronts in maintenance or inactive, a test purchase of the best seller of the last two weeks with the payment methods really offered, extensions installed or updated in the last 24 hours, errors in Shopware's log in the last 6 hours (failed mails included), and scheduled tasks that stopped. Nothing is ordered. Returns { causes[], fine[] }: likely causes first, and what was checked and found fine.

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": "shop_diagnose"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.11.1Nov 6, 2026

TDQS

A3.7/5.0

Behavior1/5

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

The description states it performs a 'test purchase ... with the payment methods really offered', which is a write operation creating an order/transaction. This directly contradicts the readOnlyHint=true annotation, which claims the tool does not modify state.

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?

The description is a single dense sentence listing the checks, followed by a short return-shape sentence. It is front-loaded with the diagnostic context and every clause contributes, though it could be slightly more scannable with structure.

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

Completeness4/5

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

For a complex composite diagnostic with no input parameters and no output schema, the description covers what is checked and the return shape ({ causes[], fine[] }). It omits that the test purchase may create real data, but that gap is tied to the annotation contradiction.

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 has zero parameters, so parameter semantics baseline is 4. The description does not need to explain parameters and adds no unnecessary parameter details.

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 states a specific diagnostic purpose: identifying why orders stop by checking storefront status, test purchases, extensions, logs, and scheduled tasks in one call. It is clearly distinct from siblings like shop_audit or shop_pulse, which are broader health checks.

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?

It clearly says when to use it: 'when orders stop or customers complain'. However, it does not name alternatives or explicitly say when not to use it, such as for general shop health checks covered by shop_audit or shop_pulse.

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