Let a caller learn what a product commits to, and by when

Orderdetail now carries requireddate and order_status, denormalised from the
order the line belongs to — filtering by product and status already answers
the question this used to need a second call per order for.

list_orders also gained a status filter, matching the backend capability that
list_order_details already exposes.

Regenerated with generate-mcp-tools.py.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Stéphane Tailland
2026-08-31 15:42:36 +02:00
parent 011e31295f
commit a2bf84eb22
2 changed files with 83 additions and 2 deletions
+18 -1
View File
@@ -219,9 +219,15 @@ paths:
/sales/v1/orders/:
get:
operationId: list_orders
description: Retrieve a paginated list of all customer orders with their status and details.
description: Retrieve a paginated list of all customer orders with their status and details. Filter by status to find open commitments, e.g. In Process or On Hold.
summary: List all orders
parameters:
- name: status
required: false
in: query
description: 'Only orders with this status, e.g. In Process, On Hold, Shipped, Cancelled, Disputed, Resolved.'
schema:
type: string
- name: page
required: false
in: query
@@ -508,6 +514,15 @@ components:
id:
type: integer
readOnly: true
requireddate:
type: string
format: date
readOnly: true
description: The order's required date. Denormalised from the order this line belongs to, so a caller filtering by product does not need a second call to learn what it commits to and by when.
order_status:
type: string
readOnly: true
description: 'The order''s status, e.g. In Process, On Hold, Shipped, Cancelled, Disputed, Resolved.'
quantityordered:
type: integer
maximum: 2147483647
@@ -528,11 +543,13 @@ components:
type: string
required:
- id
- order_status
- orderlinenumber
- ordernumber
- priceeach
- productcode
- quantityordered
- requireddate
OrderdetailRequest:
type: object
description: Order line items with product details