Skip to main content
Glama
vmware-skills

vmware-pilot

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

run_workflow

Advance a planned VMware workflow through approval gates, pausing for human sign-off and returning pending steps when external dispatch is required.

Instructions

[WRITE] Advance a planned workflow. Pauses at approval gates.

IMPORTANT — this MCP server has no dispatcher and cannot call other skills' MCP tools itself. Steps are recorded as 'not_executed' and the run finishes with outcome='dispatch_required' (NOT 'completed'), returning each pending step's skill/tool/params. YOU (the calling agent) must then perform those skill/tool calls in order. A workflow only reaches 'completed' when every step genuinely executed via a real dispatcher (embedders supplying one to WorkflowExecutor).

Safety: the workflow is structurally reviewed before each run. Runs are REFUSED if review finds ungated destructive or unclassifiable steps, or destructive steps inside a parallel group. For a built-in template, force=True overrides that (forced runs are written to the workflow audit log). For a custom workflow (create_workflow, design_workflow, or a YAML template) an ungated step is refused even with force=True: add a require_approval step before it instead.

When an approval gate is reached, the workflow pauses with state 'awaiting_approval'. Call approve() to continue.

Returns: Current workflow state with 'outcome' (completed | awaiting_approval | dispatch_required | failed) and, when dispatch is required, a 'pending_dispatch' list of steps for the agent to perform.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoBypass blocking review findings on a built-in template. Use only with explicit human consent; the bypass is audited. Has no effect on a custom workflow's missing approval gate.
workflow_idYesThe workflow ID from plan_workflow.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.11.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / force / description
      Added value: +"Bypass blocking review findings on a built-in template. Use only with explicit human consent; the bypass is audited. Has no effect on a custom workflow's missing approval gate."
    • addedInput schema / properties / workflow_id / description
      Added value: +"The workflow ID from plan_workflow."
  2. Changed1 schema field changedv1.5.38
    • addedInput schema / properties / force
      Added value: +{
+  "default": false,
+  "title": "Force",
+  "type": "boolean"
+}
  3. First observedv1.5.22

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only provide readOnly/idempotence/destructive/open-world hints, so the description carries the behavioral burden. It adds the important no-dispatcher execution model, recording of 'not_executed' steps, audit logging of forced runs, refusal conditions, and the fact that 'completed' only happens with a real dispatcher. This is far more than the annotations alone could convey.

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?

Longer than minimal, but the tool is complex and every paragraph serves a distinct purpose: execution model, safety review, approvals, and return values. The critical no-dispatcher caveat is front-loaded, and the use of bolded terms helps structure the content without redundancy.

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?

Even without an output schema, the description fully documents the possible outcome values, the pending_dispatch list, refusal conditions, and the agent's subsequent responsibilities. For a mutation tool with security-relevant behavior and a dispatcher gap, this is complete enough for an agent to invoke it correctly and know what to do next.

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. The description adds valuable meaning beyond the schema by explaining that force bypasses review findings only on built-in templates, is audited, and has no effect on custom workflows. This extra nuance helps the agent use the force parameter correctly.

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?

States a specific verb ('Advance') and resource ('a planned workflow'), and specifies the pause-at-approval behavior. It also differentiates itself from siblings by telling the agent to call approve() to continue after an approval gate, making it clear this tool is the execution step, not the approval step.

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 and when-not-to-use guidance: runs are refused for ungated destructive steps, force only applies to built-in templates, custom workflows require an added require_approval step, and approval gates require approve(). It also tells the agent it must perform the pending skill/tool calls itself when dispatch_required is returned, which is a critical routing instruction.

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