What we build
Isah does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.
# isah-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_production_orders: # project or date range -> production orders with status
backend: confirmed in blueprint
mode: read
get_part_info: # part code -> revision, stock and open orders
backend: confirmed in blueprint
mode: read
get_project_bom: # project -> BOM lines and material status
backend: confirmed in blueprint
mode: read
list_purchase_proposals: # item or supplier -> open purchase proposals
backend: confirmed in blueprint
mode: read
draft_purchase_order: # proposal -> purchase order draft for a person to confirm
backend: confirmed in blueprint
mode: propose
audit: every call logged with user, tool, arguments and the Isah 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.