Update to StewAI

{
  "description": "Use the StewAI MCP plugin to discover workflow examples, search and preview live recipes after email sign-in, estimate credits, run recipes, and retrieve final declared results without managing an API key. Use when the user mentions the StewAI plugin, StewAI MCP, or wants keyless access to an existing StewAI recipe. Do not use for Python SDK or recipe-authoring work.",
  "included_files": [
    {
      "relative_path": "LICENSE",
      "size_in_bytes": 10776
    }
  ],
  "name": "stewai-mcp",
  "skill_md_contents": "---\nname: stewai-mcp\ndescription: \"Use the StewAI MCP plugin to discover workflow examples, search and preview live recipes after email sign-in, estimate credits, run recipes, and retrieve final declared results without managing an API key. Use when the user mentions the StewAI plugin, StewAI MCP, or wants keyless access to an existing StewAI recipe. Do not use for Python SDK or recipe-authoring work.\"\n---\n\n# StewAI MCP\n\nUse StewAI recipes through the plugin without installing a package or managing an API key.\n\n## MCP-only routing\n\nUse only the StewAI MCP tools listed below. Never fall back to the Python SDK, an API key, a\nbrowser search, shell commands, or workspace files when an MCP tool needs authentication or is\nunavailable. Ask the user to connect or reauthenticate StewAI, then retry the same MCP tool.\n\n## Access model\n\n`discover_stewai` is anonymous and returns fixed workflow examples. Every live marketplace,\npreview, execution, status, or result request starts with a one-time email sign-in.\n\n## Tools\n\n<!-- BEGIN TOOL TABLE -->\n\n| Tool                 | Auth          | Purpose                                                                 |\n| -------------------- | ------------- | ----------------------------------------------------------------------- |\n| `discover_stewai`    | none          | Show fixed examples of what StewAI can automate.                        |\n| `search_recipes`     | email sign-in | Search the live marketplace with a meaningful query.                    |\n| `get_recipe_preview` | email sign-in | Preview safe labels, synthetic inputs, outputs, and historical pricing. |\n| `run_recipe`         | email sign-in | Estimate credits or run a previewed recipe idempotently.                |\n| `get_run`            | email sign-in | Read caller-owned status and terminal billing settlement.               |\n| `get_results`        | email sign-in | Read available final author-declared outputs for a completed owned run. |\n\n<!-- END TOOL TABLE -->\n\n## Recipe references and inputs\n\n`search_recipes` returns an opaque `recipe_ref`. Pass that reference to `get_recipe_preview`. The\npreview returns a refreshed `recipe_ref`; pass that preview-issued reference to `run_recipe`. A\nreference is bound to the signed-in account and expires after one hour. Search again when a\nreference is stale. Never replace it with a recipe ID.\n\nThe preview names accepted inputs as `input_1`, `input_2`, and so on. Send only those synthetic\nhandles to `run_recipe`.\n\n## Estimate, execute, and read\n\nSearch and preview return a `pricing` object based only on the recipe's historical average across\nsuccessful runs. Its `credit_band` is context, not an input-aware estimate or affordability\ncheck. Always call `run_recipe` with `dry_run: true` before recommending or starting execution.\n\nEvery `run_recipe` call, including a dry run, requires a valid `idempotency_key`. Call it with\n`dry_run: true` to receive `estimated_credits`, `available_credits`, and `sufficient` without\nexecuting or consuming that key. For a real run, provide a fresh key. Reusing a consumed key with\nthe same request returns the same run. Reusing it with changed inputs is a conflict.\n\nIf `run_recipe` returns `account_unavailable`, the signed-in identity does not have a runnable\nStewAI workspace. Do not change or retry the recipe inputs. Ask the user to reconnect with an\nordinarily provisioned Free account or contact StewAI support for account repair.\n\nThe client may ask the user to confirm a real run because `run_recipe` is marked destructive and\nopen-world. Use `get_run` to check status. After the run is terminal, continue polling `get_run` at\nits supplied interval while `billing.state` is `pending`, stopping after the 300-second settlement\nwindow. A settled response reports the authoritative run-tree charge; tokens allowed to run also\nreceive the account's current available balance and its timestamp. Do not interpret that balance\nas this run's isolated before/after effect. If billing becomes `unavailable`, explain that the\ncharge could not be verified through the connector.\n\nCall `get_results` only when the status is `done` and `results_available` is `true`. A successful\nresult contains only the final author-declared outputs as `{label, value}` entries. Billing never\ncomes from `get_results`. If the response is `result_unavailable` or `result_too_large`, explain\nthat no declared result payload is available; do not look for internal run data instead.\n\n## Not available\n\n<!-- BEGIN NOT-AVAILABLE -->\n\nThis plugin does not provide a recipe specification, graph, nodes, edges, step ids, internal\nprompts, models, parameters, code, output schemas, execution contracts, or run traces. No tool\nnamed `get_recipe`, `get_recipe_spec`, `list_recipes`, `export_recipe`,\n`get_execution_contract`, or `get_run_steps` exists. There is no browse or list-all mode.\nSearch requires a real query.\n\n<!-- END NOT-AVAILABLE -->\n\n## Starter prompts\n\n<!-- BEGIN STARTER PROMPTS -->\n\nWhat can StewAI help me automate?\nShow me examples of StewAI workflows.\nFind a live StewAI recipe for contract review.\nThis starts a one-time email sign-in before StewAI searches the live marketplace.\n\n<!-- END STARTER PROMPTS -->\n\n## Route related requests\n\nUse `stewai-create-recipe` when the recipe does not exist yet or needs changing. Use `stewai` when\nthe user explicitly asks to work through the Python SDK with an API key. A failed or unauthenticated\nMCP call never authorizes that fallback.\n"
}