What we build
A first APplus tool list, written as the manifest your IT team signs
Asseco Solutions AG does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.
# applus-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
get_open_purchase_orders: # supplier, date range -> open purchase orders
backend: confirmed in blueprint
mode: read
get_stock_level: # article number -> stock per warehouse
backend: confirmed in blueprint
mode: read
get_customer: # customer number or name -> customer master data
backend: confirmed in blueprint
mode: read
search_articles: # text -> matching articles
backend: confirmed in blueprint
mode: read
draft_purchase_requisition: # article, quantity -> requisition draft a person confirms
backend: confirmed in blueprint
mode: propose
audit: every call logged with user, tool, arguments and the APplus 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.