Skip to main content
Glama
Sign In
shopware-mcp

shopware-mcp

by bnymnDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Shop info

shop_info
Read-onlyIdempotent

Retrieve basic Shopware shop facts—version, edition, default currency and language, and write-tool status—to confirm the connection and orient before using other tools.

Instructions

Get basic facts about the connected Shopware shop: version, edition (Community/Commercial), default currency and default language, plus whether write tools are enabled on this server. Use it first to orient yourself or to confirm the connection works. Returns one object.

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_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the exact content of the response, including the server capability flag for write tools, which an agent needs before attempting mutations. Minor gap: no note on failure behavior when the connection is misconfigured.

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: the first front-loads what the tool returns, the second gives usage guidance, the third sets the return-shape expectation. No filler, no repetition of the title or annotations.

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?

With no output schema, the description carries the burden of explaining returns, and it does so by listing the actual fields plus 'Returns one object.' That is sufficient for an agent to know what it gets. A field-level shape or a note on error output would push it to 5, but nothing essential is missing for correct invocation.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No misleading parameter language is present.

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?

Names a specific verb and resource ('Get basic facts about the connected Shopware shop') and enumerates exactly what is returned: version, edition, default currency, default language, and whether write tools are enabled. This clearly separates it from siblings like shop_settings, shop_diagnose, or shop_pulse, which operate on configuration or health rather than static orientation facts.

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 explicit when-to-use guidance: 'Use it first to orient yourself or to confirm the connection works.' That is a clear trigger condition and a useful bootstrapping rule. It stops short of naming alternatives or when-not-to-use cases (e.g., use shop_settings for actual settings), so it is not a full 5.

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

Deploy Server

Other Tools