Validate the workflow script

Available now Validation uses static checks, a mock dry run, and backend configuration probes.

The MCP workflow tool does not validate a workflow script. Before a live run, use the CLI validator.

Run the validator

Open a shell in the directory that contains first-inspection.workflow.js. Run this command:

first-inspection.workflow.js · validation command

npx -y @automatalabs/workflows validate first-inspection.workflow.js \
  --args '{"request":"Find the source that defines the CLI commands."}'

The validator does not send a prompt to a model. The mock backend fabricates a schema-valid result.

The validator completes these checks:

1. It parses the meta literal and the JavaScript syntax.
2. It finds direct nondeterministic call expressions.
3. It runs the workflow with a mock agent backend.
4. It probes each routed ACP backend without a prompt.
5. It checks the authored model, mode, and configOptions values.

Read the result

A valid report has no static error or dry-run error. The command exits with code 0 when validation succeeds.

A backend probe error produces a warning. The warning is not a validation error.

If the probe for a backend reports an authentication error, authenticate that backend. Then run the validator again.

Read the command options

Run this command for a different validator option:

Validator options · shell command

npx -y @automatalabs/workflows validate --help

If you intentionally skip the mock dry run and backend probes, use --parse-only.

Next step

Run the validated workflow through the MCP tool.