shopware-mcp

Ready for the next Shopware update?

update_check

Read-onlyIdempotent

Check whether a Shopware update is safe before you start it: shows the next version and its security fixes, system requirement checks, and per-extension compatibility from Shopware's update service. Read-only.

Instructions

Before a Shopware update, a major one like 6.8 included: the version available next and the security issues it fixes, Shopware's own requirement checks, and for every extension whether it works with that version (compatible, update the extension first, a compatible version announced, not compatible, or not in the store so test it yourself), straight from Shopware's update service. Read-only: it never starts an update. Needs the privilege system:core:update (and system_config:read for the extensions), which setup grants with --plugin-updates. Returns { currentVersion, update, upToDate, requirements[], extensions[], summary, blockers[], notes[] }.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.11.1Nov 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real context on top: the data source is Shopware's own update service, the exact privileges required (system:core:update plus system_config:read for extensions, granted via --plugin-updates), and the five possible per-extension verdicts. This is the kind of auth and data-provenance detail annotations cannot carry.

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?

Front-loaded with purpose, then the compatibility taxonomy, then auth, then the return shape — every clause carries information. It is a single very long sentence, and the phrasing "a major one like 6.8 included" is grammatically rough, which costs a point on readability.

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 compensates by enumerating the return fields (currentVersion, update, upToDate, requirements[], extensions[], summary, blockers[], notes[]). Combined with the privilege requirements and the compatibility statuses, an agent has everything needed to call and interpret it.

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?

Zero parameters, so there is nothing for the description to disambiguate and the baseline applies. It correctly implies the call is unparameterized and target-agnostic rather than leaving the agent wondering which version to supply.

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 check (update readiness) against a specific resource (the next Shopware version, e.g. 6.8) and enumerates what the result covers: version, fixed security issues, Shopware's requirement checks, and per-extension compatibility. An agent can distinguish this from plugins_list or shop_diagnose without opening a 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?

Explicitly scopes use to "Before a Shopware update" and clarifies it never starts the update itself, which prevents the obvious misuse. It doesn't name a sibling alternative or state when not to bother running it (e.g. already up to date), so it stops short of the top score.

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