Skip to main content
Glama
superpowers-mcp

superpowers-mcp

by erophames

compose_workflow

Build an ordered, multi-skill workflow for a goal, applying guardrails and semantic relevance to sequence steps and keep execution focused.

Instructions

Compose an ordered multi-skill workflow for a goal using guardrails and semantic relevance.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "goal": "<goal>"
    },
    "name": "compose_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesThe user goal to accomplish.
max_stepsNoMaximum number of workflow steps.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden. 'Using guardrails and semantic relevance' gestures at internal logic but doesn't say whether composition consumes tokens, whether it persists a workflow object, how it reacts to unavailable skills, or whether the result is deterministic — all material for a tool that 'composes' something.

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?

A single front-loaded sentence with the verb and scope first; no filler or repetition. 'Guardrails and semantic relevance' is slightly jargon-heavy but still earns its place by hinting at selection criteria.

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

Completeness2/5

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

There is no output schema and no annotations, so the description should explain what 'compose' returns — a step list, skill references, ordering rationale — and whether anything is created or stored. For a tool whose whole value is the produced workflow, that information is absent.

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

Parameters3/5

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

Schema description coverage is 100%, so both 'goal' and 'max_steps' (with min 1 / max 12) are already documented structurally. The description adds no extra meaning about the goal's expected granularity or how max_steps interacts with guardrails, so the baseline 3 applies.

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

Purpose4/5

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

The description gives a specific verb ('Compose') plus a concrete resource ('ordered multi-skill workflow for a goal'), which distinguishes it from siblings like validate_workflow (validation) and recommend_skills (suggestion). It stops short of naming any sibling explicitly, so the differentiation is inferable rather than stated.

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

Usage Guidelines2/5

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

The only usage signal is 'for a goal', which hints at the trigger but never states when to reach for this versus validate_workflow or recommend_skills, nor any prerequisite (e.g., skills must already be discoverable). No when-not guidance is offered.

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