shopware-mcp

Get stock

stock_get

Read-onlyIdempotent

Retrieve stock and available stock for a product by ID or product number, including every variant, to answer how many units are left.

Instructions

Get stock and available stock for one product by ID or product number, including every variant. Use it for 'how many X are left?' questions. Returns one object with a variants[] list (empty for simple products).

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

Input Schema

Name	Required	Description	Default
`productId`	No	Product UUID
`productNumber`	No	Product number, e.g. SW10001

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.11.1Nov 6, 2026

TDQS

A3.8/5.0

Behavior3/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 meaningful context beyond them by disclosing the return shape (one object with a variants[] list, empty for simple products), which matters because no output schema exists. It does not address not-found behavior or whether both lookup keys can be combined.

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, front-loaded with what the tool returns, then the use case, then the response shape. No filler and nothing repeated from the schema or title.

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?

For a small two-parameter read tool with no output schema, the description covers purpose, lookup mechanism, and return structure well enough to call it correctly. The remaining gap is edge-case behavior (unknown product number, variant-level fields), which is minor at this complexity.

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?

Schema description coverage is 100% (both parameters documented with a UUID pattern and an example product number), so the schema already carries the parameter semantics. The description's 'by ID or product number' hints at an either-or choice, but with zero required parameters it does not clarify whether one must be supplied or what happens if both are.

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?

The description gives a specific verb and resource ('Get stock and available stock for one product') plus scope ('including every variant') and the two lookup keys. It does not explicitly distinguish itself from the sibling stock_forecast, so the boundary between current stock and forecast is left for the agent to infer.

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?

The sentence 'Use it for "how many X are left?" questions' gives a concrete usage context that maps a user intent to this tool. There are no explicit exclusions or named alternatives (e.g. stock_forecast for future availability), which keeps it short of a 5.

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