Skip to main content
Glama
superpowers-mcp

superpowers-mcp

by erophames

validate_workflow

Checks whether chosen skills satisfy a goal's required guardrails and, when order enforcement is enabled, confirms required skills come before optional ones.

Instructions

Validate whether selected skills satisfy required guardrails for a goal.

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>",
      "selected_skills": "<selected_skills>"
    },
    "name": "validate_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesThe goal that determines workflow intent.
enforce_orderNoIf true, required skills must come before optional skills.
selected_skillsYesSkills selected or already used, in order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing beyond the purpose. It does not say whether validation is purely read-only, what a failed validation produces (error vs. a list of violated guardrails), whether missing required skills are reported individually, or how enforce_order affects the verdict.

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 no filler or redundancy, sized appropriately for the tool. It is efficient but very sparse for a validation tool whose result semantics matter to the caller.

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?

The tool has no output schema, so the description is the only place the agent can learn what a validation result looks like, and it is silent on that. Given that the entire value of the tool is its pass/fail verdict, omitting outcome semantics leaves a material gap even though the input schema is fully documented.

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 each of the three parameters is already documented, and the description adds only the framing that goal determines workflow intent and that skills are checked against guardrails. It clarifies the relationship between the two required parameters but adds no new syntax or constraint detail beyond the schema.

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 names a specific verb ("Validate") and a specific subject (whether selected skills satisfy required guardrails for a goal), which is far more informative than the bare name. It does not, however, distinguish itself from siblings like compose_workflow or recommend_skills, so an agent cannot tell from the text alone whether validation is a pre-compose gate or a standalone check.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the phrase "selected skills" suggests it is run after a skill selection exists, and "for a goal" ties it to goal context. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g., precede compose_workflow), leaving the agent to infer the workflow position.

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