StewAI

Run free deterministic lint, render, policy, and compiler checks. Omit fixtures for the normal structural check; a supplied fixture probe must also provide every referenced upstream dependency value.

check_recipe_build

Preflight and privately publish only the exact fully qualified recipe revision. A successful commit returns a private editor URL and, when current run access permits it, a recipe_ref. Preview that reference before any dry run: authoring contract handles and node IDs are not the positional input_N run handles. The recipe stays private, unlisted, and unreviewed; commit never lists, prices, or publishes it in the public marketplace.

commit_recipe_build

Learn how any MCP agent can authenticate, discover, preview, run, author, qualify, commit, inspect, and recover StewAI recipes. Call this first.

discover_stewai

After a finished run, read view=steps with detail=full first and follow next_cursor; every step the user paid for is part of the result. Declared outputs are the pinned summary, not the whole result. Read declared outputs or a sanitized per-step trace from an owned run, including signed chunks for oversized steps. view=steps returns compact summaries, 10 per page by default and at most 20 (limit 1-20); follow next_cursor until it is null, pass detail=full for whole steps, or use view=step with step_id for one full step. Open recipes expose all authorized steps; closed recipes expose only input and output steps. Sensitive values stay redacted. Step reads are provisional until get_run reports a finished status. If outputs is empty, read view=steps; for a failed run, read the failed step and let the user decide. Present completed outputs as polished Markdown or text: lead with the useful outcome, add At a glance, supported strengths, impact-ordered findings, and concrete next steps; end with evidence, uncertainty, limitations, charged credits, and a clickable run link using run_url with the run ID as its label. Render JSON as readable tables or bullets and HTML as content, not markup. Cross-check material claims against supplied source and cited evidence; describe unsupported or high-stakes conclusions as findings to verify. Say blocking only when the recipe explicitly classifies the item that way and evidence supports it. Keep diagnostics, safety ceilings, and platform plumbing out of the main answer; billing receipt issues stay quiet and never suppress ready results.

get_results

Read an owned run, view=history to resume normal runs (recipe_ref/status/cursor/limit), or view=diagnostics for its settled UI receipt. Default status requires run_id.

get_run

Poll a review or acceptance batch through a bounded, disclosure-safe view.

get_recipe_build_activity

List or inspect only the authenticated creator's private recipe builds. To list builds omit both build_ref and view; limit/cursor paginate that list. With or without build_ref, use view='authoring_schema' and schema_name='update_recipe_build', 'acceptance_suite', or 'start_recipe_build' to read the complete executable JSON Schema when a client hides nested operation or assertion fields. Large acceptance_plan reads return data.suite_page JSON fragments: append content in offset order, pass data.next_cursor as cursor until null, then parse the complete suite and verify its sha256. Small plans retain data.suite. Use view='capabilities' to discover the complete 24-handler authoring and automatic-acceptance capability catalog.

get_recipe_build

Inspect a safe summary with bounded method and limitations excerpts, output-contract state, and evidence context. For complete authorized published details and executable contracts, use view=details. Concatenate content fragments in offset order per section; decode JSON sections after completion. Use next_cursor with the same recipe_ref until null. Opaque internals remain withheld.

get_recipe_preview

Quote or run a bounded semantic quality review of the exact private draft revision.

review_recipe_build

Execute a previewed recipe using its opaque reference and synthetic input handles.

run_recipe