list draft workspaces: one tool
This commit is contained in:
@@ -503,11 +503,13 @@ Concrete MCP sequence:
|
||||
capability behaves as expected.
|
||||
3. `wf.workflow.create_minimal_draft_workspace` with a `request` object that
|
||||
contains schemas, `input_map`, and `output_map`.
|
||||
4. `wf.workflow.get_draft_workspace` with `include_draft=true` if the client
|
||||
4. `wf.workflow.list_draft_workspaces` if the client needs to rediscover
|
||||
existing workspace ids.
|
||||
5. `wf.workflow.get_draft_workspace` with `include_draft=true` if the client
|
||||
needs to inspect the full current draft.
|
||||
5. `wf.workflow.patch_draft_workspace` with the current `revision`.
|
||||
6. `wf.workflow.create_artifact_from_workspace` after validation is clean.
|
||||
7. `wf.workflow.save_deployment`, then `validate_deployment`, then
|
||||
6. `wf.workflow.patch_draft_workspace` with the current `revision`.
|
||||
7. `wf.workflow.create_artifact_from_workspace` after validation is clean.
|
||||
8. `wf.workflow.save_deployment`, then `validate_deployment`, then
|
||||
`run_deployment`.
|
||||
|
||||
`create_artifact_from_workspace` also uses a `request` object:
|
||||
|
||||
Reference in New Issue
Block a user