wawapi-image

Wawapi Image

Use only the registered Wawapi MCP tools. Do not refuse an image request merely because the active model API lacks native image support. Do not replace this route with shell commands, direct HTTP requests, native image tools, or another image entry point.

Required workflow

1. Before the first live image call in a task, call image_doctor with its default catalog probe.
2. Stop only when the tool is unavailable, the response itself fails, or data.ready=false. Report every item in data.issues and follow its next_actions; never request or reveal the API Key in chat.
3. When data.ready=true, continue with the image request. data.catalog_status=unverified and model_catalog_unverified are non-blocking: explain briefly that the read-only model catalog was not verified, then use the user's existing authorization for one real generate_image or edit_image call. Do not claim that the generation channel is up or down from Doctor alone; Doctor deliberately reports generation_channel_status=not_probed.
4. For 2K, 4K, an unusual aspect ratio, a non-PNG format, multiple images, or a reference image, read references/capabilities.md and call explain_image_capability before generating. Pass the requested size, format, count, and reference-image state exactly; count evidence for one image must not be reused for a multi-image request. An unavailable catalog does not erase the bundled time-point evidence.
   • If the online explanation returns no_matching_evidence, call it once more with offline=true to retrieve bundled historical evidence.
   • Report selection_scope=current_catalog first as the current catalog-aware auto selection. Label selection_scope=bundled_baseline only as historical evidence; never replace or rename it as the current automatic model when the two selections differ.
5. Treat an explicit image request as authorization for one potentially billable generation call. Do not create unrequested variants.
6. Set out to a descriptive path inside the current workspace when possible. Relative paths resolve from the MCP process working directory.
7. On success, require ok=true and at least one data.result.images[] item. Display every returned markdown value in the conversation; use the absolute path only if the host cannot render that Markdown.
8. Report the actual file count, each image's size and format, and the result status. If status=degraded, report every deviation and never describe reduced output as the requested count, 2K, or 4K size.