shopware-mcp

Check promotions before a campaign

promotions_check

Read-onlyIdempotent

Check all Shopware promotions running or starting before a date to flag inactive, discountless, code, channel, limit, overlap, and timing issues before a sale.

Instructions

Before Black Friday or any sale: check every promotion that runs or starts before a date, active or not, the way Shopware decides whether it applies. Flags a promotion that starts but is still inactive, has no discount, no sales channel or only channels in maintenance, needs a code but has none, has no unused individual codes left, is close to its redemption limit, gives 50 % or more, ends before it starts, or applies automatically together with another one so the discounts add up. Read-only. Returns { window, checked, summary, promotions[] } with findings per promotion, worst first.

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

Input Schema

Name	Required	Description	Default
`until`	No	End of the campaign window, ISO date (a date covers the whole day). Default: in 14 days

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.11.1Nov 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bare 'Read-only' sentence earns nothing, but the description goes well beyond them: it enumerates the nine failure conditions flagged and states the result ordering ('worst first'). Only minor gaps remain, such as how many promotions a default window can return.

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 usage trigger is front-loaded and the return shape closes it, with no filler. The middle sentence is a long comma-chained list of nine conditions that reads as a run-on; it is dense with real content rather than padding, but bullet-like separation would have been more scannable.

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 return contract itself and does so precisely: '{ window, checked, summary, promotions[] }' with per-promotion findings ordered worst first. For a single-parameter read tool whose annotations already declare safety, nothing an agent needs in order to call it correctly 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?

Schema coverage is 100% and the single parameter already documents ISO format, whole-day handling and the 14-day default, so the baseline is 3. The description adds selection semantics the schema does not: promotions that merely *start* before the cut-off are included, and the value is treated as the end of a campaign window rather than a point lookup.

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?

Specific verb ('check') plus resource ('every promotion') plus scope ('runs or starts before a date, active or not') and an explicit fidelity claim ('the way Shopware decides whether it applies'). This distinguishes it from the sibling promotions_list (enumeration) and promotion_impact (impact modelling) without the agent needing to open 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 Guidelines4/5

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

Frames the trigger situation concretely: 'Before Black Friday or any sale'. It tells the agent when to reach for it but never names the alternatives (promotions_list, promotion_impact) or says when not to use it, so routing still requires the sibling names to be self-explanatory.

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