shopware-mcp

List plugins and apps

plugins_list

Read-onlyIdempotent

Lists installed plugins and apps with version, active state, and available upgrades so you can check whether an extension is installed or outdated.

Instructions

List installed plugins and apps with version, active/installed state and the available upgrade version (when the shop can reach the Shopware store). Use it to check whether an extension is installed or outdated. Returns { total, items[] }.

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

Input Schema

Name	Required	Description	Default
`type`	No	Filter by extension type	all
`activeOnly`	No	Only return active extensions

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.11.1Nov 6, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds one genuinely useful behavioral caveat – upgrade version is only populated when the shop can reach the Shopware store – plus the { total, items[] } shape. It does not discuss pagination or how a large extension list is returned.

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?

Three short sentences, zero filler, with purpose and the field list front-loaded before the usage hint and return shape. Every sentence contributes something an agent can act on.

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?

For a two-optional-parameter read-only list tool with no output schema, the description supplies the return shape and the key limitation on upgrade data, which is everything an agent needs to call it and interpret the result correctly.

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 description coverage is 100%, so both parameters (type with its enum, activeOnly) are fully documented in the schema; the baseline is 3. The description's mention of 'installed plugins and apps' and 'active/installed state' lightly reinforces what type and activeOnly control, pushing it just above baseline.

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

Purpose4/5

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

States a specific verb ('List') and resource ('installed plugins and apps') and enumerates the fields surfaced (version, active/installed state, available upgrade version). It is clear what separates this from update_check by implication ('check whether an extension is installed or outdated'), but it never names that sibling or any other, so differentiation is inferred rather than stated.

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?

Gives an explicit when-to-use condition: 'Use it to check whether an extension is installed or outdated.' There is no when-not guidance and no pointer to update_check or shop_diagnose when the question is about core or store-level health rather than extensions.

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