Skip to main content
Glama
Sign In
Superpowers MCP

Superpowers MCP

by xinyuzjj
OverviewSchemaSourceRelated ServersDiscussionsAdmin

list-superpower-skills

Discover available superpower skills in the Superpowers MCP framework to access advanced capabilities for AI-driven development tasks.

Instructions

List all available superpowers skills

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list-superpower-skills"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:36-43 (registration)
    Registration of the 'list-superpower-skills' tool definition.
    {
  name: 'list-superpower-skills',
  description: 'List all available superpowers skills',
  inputSchema: {
    type: 'object',
    properties: {},
  },
},
  • src/index.ts:81-91 (handler)
    The handler implementation for 'list-superpower-skills'. It is currently a placeholder.
    case 'list-superpower-skills': {
  // TODO: Implement skills listing logic
  return {
    content: [
      {
        type: 'text',
        text: 'Available skills: ...',
      },
    ],
  }
}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool lists skills but doesn't disclose behavioral traits like whether it's read-only, requires authentication, has rate limits, or returns paginated results. This is a significant gap for a tool with zero annotation coverage.

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 a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary details.

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?

Given the tool's simplicity (0 params, no output schema), the description is minimal but incomplete. It lacks behavioral context (e.g., read-only nature, response format) that would help an agent use it correctly, especially with no annotations to compensate.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is fine here. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs.

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

Purpose3/5

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

The description states the tool's purpose ('List all available superpowers skills') with a clear verb ('List') and resource ('superpowers skills'), but it's vague about scope—does 'available' mean globally or user-specific? It doesn't distinguish from the sibling tool 'run-superpower-command', which appears to execute rather than list skills.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention the sibling tool 'run-superpower-command' or clarify if this is for discovery before execution. Usage context is implied but not explicit.

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