What we build
A first PAS-X tool list, written as the manifest your IT team signs
Built on what Körber, Business Area Pharma (formerly Werum IT Solutions) documents: batches and electronic batch records, process orders, materials, process exceptions, weighing and dispensing records, equipment status and cleaning, KPI and OEE, serialisation data. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.
# pas-x-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
list_open_exceptions: # product or site, date range -> batches with open exceptions and category
backend: PAS-X Data Access, SQL views confirmed in blueprint
mode: read
get_batch_status: # batch id -> order, status, current step, review state
backend: PAS-X Data Access, resource confirmed in blueprint
mode: read
get_material_consumption: # batch id -> consumed material lots and quantities
backend: PAS-X Data Access, resource confirmed in blueprint
mode: read
get_order_list: # site, date range -> process orders with status
backend: PAS-X Data Access, resource confirmed in blueprint
mode: read
audit: every call logged with user, tool, arguments and the PAS-X response
The manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.