Skip to main content
Glama
vmware-skills

vmware-pilot

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_workflow

Build a custom workflow from a step list when no built-in template fits, with approval gates and rollback options. Define steps, validate, and get a workflow ID for review and execution.

Instructions

[WRITE] Create a custom workflow dynamically from a step list.

Use this when you already know the steps and no built-in template matches; prefer plan_workflow when one does, and design_workflow when the user gave a goal rather than steps. Call get_skill_catalog first for the skill and tool names a step may target.

Each step dict must have: action, skill, tool, params. Optional: rollback_tool, rollback_params. action="require_approval" (skill "pilot", tool "approve") inserts a human approval gate. A workflow whose destructive or unclassifiable step, or a step passing confirm=True, has no gate before it is REFUSED — nothing is saved — and the error names the step and the gate to insert.

Returns: dict with workflow_id and plan summary. Next call review_workflow to check the plan, then run_workflow to execute. Nothing is undone automatically on failure; see rollback.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesWorkflow name (used as workflow_type).
stepsYesList of step dicts, each with action/skill/tool/params.
descriptionYesHuman-readable description.
save_as_templateNoIf True, save as YAML to ~/.vmware/workflows/ for reuse. Refused when name is a built-in template's name, since the saved template would replace the built-in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.11.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / description / description
      Added value: +"Human-readable description."
    • addedInput schema / properties / name / description
      Added value: +"Workflow name (used as workflow_type)."
    • addedInput schema / properties / save_as_template / description
      Added value: +"If True, save as YAML to ~/.vmware/workflows/ for reuse. Refused when name is a built-in template's name, since the saved template would replace the built-in."
    • addedInput schema / properties / steps / description
      Added value: +"List of step dicts, each with action/skill/tool/params."
  2. First observedv1.5.22

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description discloses critical behavioral rules: steps without approval gates for destructive/confirm=True operations are refused with nothing saved, the error names the step and gate, and failures are not automatically rolled back. This adds real operational context that the sparse annotations do not capture.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every section earns its place: purpose, usage routing, step contract, refusal behavior, return value, and next actions. It is front-loaded with the core purpose and usage guidance, and the later paragraphs organize constraints and follow-up steps logically.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema and complex nested step objects, the description covers why, when, how, what can fail, what the return looks like, and which sibling to call next. The edge-case behavior around approval gates and rollback is exactly the kind of contextual detail an agent needs to invoke this tool safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds substantial meaning for the steps parameter: required and optional keys, the require_approval action convention, and the confirm=True refusal condition. It does not need to explain every schema field, but it enriches the most complex parameter well beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Create a custom workflow dynamically from a step list') and distinguishes this tool from siblings by clarifying it is for known steps with no matching built-in template. It names plan_workflow and design_workflow as alternatives, making the tool's niche unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use this tool ('when you already know the steps and no built-in template matches') and when to prefer alternatives with concrete conditions ('prefer plan_workflow when one does, and design_workflow when the user gave a goal rather than steps'). It also instructs the agent to call get_skill_catalog first, which is actionable and specific.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools