Skip to main content
Glama
superpowers-mcp

superpowers-mcp

by erophames

use_skill

Load a named superpowers skill to retrieve its full instructions; optional guardrails enforce required workflow order for the current goal.

Instructions

Load a superpowers skill by name. Returns the full skill content to follow as instructions. Optional guardrails can enforce required workflow order for the current 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": {
      "name": "<name>"
    },
    "name": "use_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNoCurrent task goal. Used when enforce_guardrails is true.
nameYesThe skill directory name (e.g. 'brainstorming', 'test-driven-development')
enforce_guardrailsNoIf true, block this skill when required guardrail skills are missing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the safety burden and does disclose the important trait that the returned content is meant to be followed as instructions, plus that guardrails can block a load. It omits what happens on an unknown skill name, whether a successful load records state, and whether guardrail blocks return an error or a partial result.

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?

Three short sentences, front-loaded with the action and required input, then the return value, then the optional guardrail behavior. No filler and nothing redundant with the schema.

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

Completeness4/5

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

No output schema exists, and the description correctly covers the return ('full skill content to follow as instructions'). Missing only failure behavior and guardrail-block semantics, which are minor for a simple three-parameter loader.

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 coverage is 100%, so each parameter is already documented; the description only adds the linkage that 'goal' matters when guardrails are enforced and that guardrails gate on missing prerequisite skills. That is a useful framing but not new per-parameter semantics 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?

States a specific verb and resource ('Load a superpowers skill by name') and clarifies the result is the skill body, not a listing or metadata. It does not differentiate itself from siblings such as get_skill_file or list_skills, so an agent must infer which loader to pick.

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 only implied: load a skill before following it, and optionally turn on guardrails to enforce workflow order. There is no explicit when-to-use vs. when-to-use-a-sibling guidance (e.g., load vs. get_skill_file) and no stated prerequisites for obtaining a valid skill name.

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