shopware-mcp

Get order

orders_get

Read-onlyIdempotent

Retrieve a single order by ID or order number with line items, addresses, payments, and shipments to answer detailed questions about that order.

Instructions

Get one order by ID or order number with line items, billing/shipping addresses, transactions (payment method and state) and deliveries (shipping method, tracking codes). Use it to answer detailed questions about a single order. 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": "orders_get"
  }
}

Input Schema

Name	Required	Description
`fields`	No	Extra raw entity fields to add to each item, e.g. ['customFields', 'ean']. Dot-paths allowed.
`orderId`	No	Order UUID
`orderNumber`	No	Order number as shown to customers

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.11.1Nov 6, 2026

TDQS

A3.6/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 safety is covered. The description adds the return payload shape ('Returns one object' with named sections), but says nothing about what happens when neither identifier is supplied, when both are supplied, or what error/empty behavior to expect from a zero-required-param lookup.

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?

Three short sentences, front-loaded with the identifier and the returned resources, with 'Returns one object' closing efficiently. No filler, though that final sentence borders on restating the obvious for a singular getter.

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 usefully enumerates the returned sections, and annotations carry the safety profile. The only material gap for a 3-param, zero-required lookup is the undisclosed rule for choosing or combining orderId and orderNumber.

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%, so the schema already documents fields, orderId and orderNumber, making the baseline 3. The description adds nothing about the selection rule between the two identifiers (which wins if both are passed, whether one is mandatory) or about the 'fields' escape hatch, so it does not exceed the schema.

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 opens with a specific verb and resource ('Get one order by ID or order number') and enumerates the sub-resources returned (line items, addresses, transactions, deliveries). It implicitly separates itself from orders_search by emphasizing a single order, though it never names the sibling explicitly.

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?

'Use it to answer detailed questions about a single order' gives clear when-to-use context and signals the detail-heavy nature of the payload. It stops short of an explicit exclusion such as 'if you only have a search term, use orders_search instead.'

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