Skip to main content
Glama
vmware-skills

vmware-pilot

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_workflow

Create a custom workflow from a step list when no built-in template matches. Define steps with action, skill, tool, and params, plus optional rollback and approval gates.

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 create_workflow_from_template 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.8/5.0
Behavior5/5

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

Annotations only supply readOnlyHint=false and destructiveHint=false; the description goes well beyond that by disclosing the required step schema, the approval-gate mechanism (action='require_approval', skill 'pilot', tool 'approve'), and the refusal behavior that names the offending step when a destructive/confirm=True step lacks a gate. It also states the return value, the follow-up sequence, and that nothing is undone automatically on failure.

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

Conciseness4/5

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

Front-loaded with the [WRITE] tag and one-line purpose, then usage routing, then mechanics. The refusal paragraph is dense but load-bearing; the Returns block is slightly more verbose than necessary, keeping it just short of maximum.

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?

With no output schema, the description carries the return contract (workflow_id + plan summary) and the recommended next calls (review_workflow, then run_workflow), plus rollback expectations. For a mutation tool with a validation-refusal path, this is complete enough to drive correct use.

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 description coverage is 100%, so the baseline is 3, but the description adds real semantics the schema lacks: the exact step keys (action, skill, tool, params plus optional rollback_tool/rollback_params) and the special require_approval action values. It does not elaborate on save_as_template beyond what the schema already states.

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?

Opens with '[WRITE] Create a custom workflow dynamically from a step list,' naming a specific verb, resource, and input mode. It explicitly distinguishes itself from two siblings (create_workflow_from_template and design_workflow), so an agent can route without reading schemas.

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?

Gives explicit when-to-use ('you already know the steps and no built-in template matches'), names the two alternatives with the exact conditions that select them, and adds a prerequisite ('Call get_skill_catalog first for the skill and tool names'). Nothing is left to inference.

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