Skip to main content
Glama
xinyuzjj

Superpowers MCP

by xinyuzjj

run-superpower-command

Execute commands within the Superpowers framework to access advanced AI-driven capabilities like automated planning, debugging, and parallel development.

Instructions

Run a superpowers command

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesThe command to run
argsNoArguments for the command

Implementation Reference

  • The handler function for the `run-superpower-command` tool. Note that it currently just returns a confirmation string as a placeholder.
    case 'run-superpower-command': {
      const { command, args = [] } = request.params.arguments as any
      // TODO: Implement command execution logic
      return {
        content: [
          {
            type: 'text',
            text: `Command "${command}" executed with args: ${JSON.stringify(args)}`,
          },
        ],
      }
    }
  • src/index.ts:16-35 (registration)
    The definition and registration of the `run-superpower-command` tool within the MCP server's tools list.
    {
      name: 'run-superpower-command',
      description: 'Run a superpowers command',
      inputSchema: {
        type: 'object',
        properties: {
          command: {
            type: 'string',
            description: 'The command to run',
          },
          args: {
            type: 'array',
            items: { type: 'string' },
            description: 'Arguments for the command',
            default: [],
          },
        },
        required: ['command'],
      },
    },
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states the action ('Run a superpowers command') without any information about side effects, permissions required, rate limits, error handling, or what happens upon execution. This is inadequate for a tool that likely performs mutations or operations with potential consequences.

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?

The description is extremely concise with a single sentence, 'Run a superpowers command', which is front-loaded and wastes no words. While it is under-informative, it does not suffer from verbosity or poor structure, earning full marks for conciseness.

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

Completeness1/5

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

Given the lack of annotations and output schema, the description is incomplete for a tool with potential complexity. It fails to explain what 'superpowers' entails, what commands are available, the outcome of running a command, or any behavioral traits. This leaves significant gaps for an agent to understand and use the tool effectively.

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%, with clear documentation for both parameters ('command' and 'args'). The description does not add any semantic meaning beyond what the schema provides—it mentions 'command' but offers no examples, constraints, or context for valid commands. Since the schema handles parameter documentation adequately, the baseline score of 3 is appropriate.

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

Purpose2/5

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

The description 'Run a superpowers command' is a tautology that essentially restates the tool name 'run-superpower-command'. It provides a generic verb+object but lacks specificity about what 'superpowers' refers to, what types of commands are available, or what resources are affected. While it distinguishes from the sibling 'list-superpower-skills' by implying execution rather than listing, the purpose remains vague and under-defined.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context for command execution, or comparisons to the sibling tool 'list-superpower-skills'. There is no indication of when this tool is appropriate or what scenarios it addresses, leaving the agent with no usage direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/xinyuzjj/superpowers-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server