shopware-mcp

Shop brief

shop_brief

Read-onlyIdempotent

Summarizes today's orders and payments against a usual day, audit findings, and last seven days' revenue in one read-only manager briefing.

Instructions

One look at the whole shop, as a manager wants it in the morning: orders and payments right now against a usual day, the audit's findings, and the last seven days' revenue. Hosts that show MCP Apps get it as an interactive page with charts. Read-only. Returns { headline, today, audit, last7Days } in short; use shop_pulse, shop_audit or sales_report for the details of one part.

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

Input Schema

Name	Required	Description	Default
`timeZone`	No	IANA time zone of the shop, e.g. Europe/Berlin; default: the server's

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 read-only, idempotent, non-destructive, and open-world hints, so the description isn't carrying the safety burden. It adds genuinely new behavior: hosts supporting MCP Apps receive an interactive chart page, and the response keys are { headline, today, audit, last7Days }. Its "Read-only" clause merely restates annotations, and no caching or freshness behavior is described.

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 tight sentences, front-loaded with the core value proposition, then the host-rendering caveat, then the return shape and sibling routing. No filler or repeated annotation boilerplate beyond a single word.

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 responsibly discloses the top-level return keys and notes host-dependent rendering, which an agent needs to plan. What each section actually contains (e.g., what the audit findings or headline cover) is only named, not characterized, leaving a small interpretive gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single optional timeZone parameter is fully documented in the schema, including the IANA format and a server-default fallback. The description adds nothing about it, which is acceptable at 100% schema coverage but means no extra meaning is contributed.

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 names a concrete deliverable (a whole-shop morning overview) and enumerates its parts: today's orders/payments against a usual day, audit findings, and seven-day revenue. It also distinguishes itself from shop_pulse, shop_audit, and sales_report, so an agent can route without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It states the usage context ("one look at the whole shop, as a manager wants it in the morning") and explicitly routes detail requests to three named sibling tools "for the details of one part." Both when-to-use and the alternative are given.

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