OZmoz

Use this when the user asks to build an app with OZmoz or to store an app's data with OZmoz. Creates a NEW OZmoz Cloud project. Call this ONLY when starting a brand new application from scratch. DO NOT call it if the project is already initialized (OZ_DB_KEY present in .env, or svro.schema.json exists): use 'oz_update_project' instead. This tool is already authenticated and returns the exact next command to run: no shell command or filesystem search is needed before calling it, including this tool's own JSON definition file (e.g. under ~/.gemini/.../mcp/ozmoz/oz_create_project.json) — you already have this schema in context via the tool list. Only if it returns a missing-token error: run 'npx ozmoz login' once, wait for it to finish, then call this tool again.

HARD STOP: call this tool ONLY after the user has explicitly approved the screens in a message that arrived AFTER you gave them the dev-server address (first sealing), or when they ask for a data change (later). NEVER in the same turn as writing UI code or asking for their approval: if they have not answered yet, ask and STOP. 'userApproval' must be their exact words. Models / updates the project's data contract (svro.schema.json + svro.workflow.json) from UI component files and business rules, additively. This is the ONLY way to evolve the contract: there is no shell command for it. Pass 'filePaths' (e.g. ['src/components/DeskList.jsx']); 'keyApp' is optional (read from .env). Do NOT read this tool's own JSON definition file from disk (e.g. under ~/.gemini/.../mcp/ozmoz/oz_update_project.json) before calling it — you already have this schema in context via the tool list; re-reading it wastes time and tokens for no new information. Before calling this tool, ask the user (like the framework question) which analysis depth they want for this modeling pass: briefly explain what this step does and what each mode costs, THEN show only the two options as a bare list (recommended option first) — and pass their LITERAL reply as 'modeReply' from your very first call. If you forget and call without it, the tool may fail and tell you to ask; that is a fallback, not the normal path. On success the sync is already done by this tool: do NOT run 'npx ozmoz sync' afterwards. If it returns an error, never run sync to fix a modeling error: call this tool again. Run 'npx ozmoz sync' once only if the error says the sync itself failed.

Deploys an OZmoz serverless function to the VM Sandbox. HARD STOP: Serverless functions incur infrastructure costs. NEVER call this tool without having explicitly explained its intent and obtained the user's explicit prior agreement.

Call this FIRST whenever the user mentions OZmoz. Provides the official data contract, SDK directives, production lifecycle and canonical blueprint.

Takes no parameters.