Skip to main content
Glama
jmcdice

Superpowers MCP Server

by jmcdice

find_skills

Discover available skills in personal and community libraries to access expert-crafted workflows for coding tasks.

Instructions

List all available skills in the personal and superpowers skill libraries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'find_skills' tool within the CallToolRequestSchema request handler. It discovers skills in personal and superpowers directories using findSkillsInDir, formats a list, and returns it as text content.
    if (name === 'find_skills') {
      const personalSkills = findSkillsInDir(personalSkillsDir, 'personal', 3);
      const superpowersSkills = findSkillsInDir(superpowersSkillsDir, 'superpowers', 3);
    
      const allSkills = [...personalSkills, ...superpowersSkills];
    
      if (allSkills.length === 0) {
        return {
          content: [{
            type: 'text',
            text: 'No skills found. Install superpowers skills to ~/.augment/superpowers/skills/ or add personal skills to ~/.augment/skills/'
          }]
        };
      }
    
      let output = 'Available skills:\n\n';
    
      for (const skill of allSkills) {
        const namespace = skill.sourceType === 'personal' ? '' : 'superpowers:';
        const skillName = skill.name || path.basename(skill.path);
    
        output += `${namespace}${skillName}\n`;
        if (skill.description) {
          output += `  ${skill.description}\n`;
        }
        output += `  Directory: ${skill.path}\n\n`;
      }
    
      return {
        content: [{
          type: 'text',
          text: output
        }]
      };
    }
  • Registration of the 'find_skills' tool in the tools list returned by ListToolsRequestSchema handler, including its description and input schema (no parameters required).
    {
      name: 'find_skills',
      description: 'List all available skills in the personal and superpowers skill libraries.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      }
    },
  • Helper function used by the 'find_skills' handler to recursively scan directories for SKILL.md files, extract frontmatter metadata, and collect skill information.
    function findSkillsInDir(dir, sourceType, maxDepth = 3) {
      const skills = [];
    
      if (!fs.existsSync(dir)) return skills;
    
      function recurse(currentDir, depth) {
        if (depth > maxDepth) return;
    
        const entries = fs.readdirSync(currentDir, { withFileTypes: true });
    
        for (const entry of entries) {
          const fullPath = path.join(currentDir, entry.name);
    
          if (entry.isDirectory()) {
            const skillFile = path.join(fullPath, 'SKILL.md');
            if (fs.existsSync(skillFile)) {
              const { name, description } = extractFrontmatter(skillFile);
              skills.push({
                path: fullPath,
                skillFile: skillFile,
                name: name || entry.name,
                description: description || '',
                sourceType: sourceType,
                dirName: entry.name
              });
            }
    
            recurse(fullPath, depth + 1);
          }
        }
      }
    
      recurse(dir, 0);
      return skills;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a list operation but doesn't mention whether it requires authentication, has rate limits, returns paginated results, or what format the output takes. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that immediately communicates the core functionality without any wasted words. It's appropriately sized for a simple list tool with no parameters, and every element of the sentence contributes to understanding what the tool does.

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

Completeness3/5

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

For a zero-parameter list tool, the description adequately covers the basic purpose. However, without annotations or an output schema, it doesn't address important behavioral aspects like authentication requirements, rate limits, or return format. The description is minimally complete but could provide more context about the operation's characteristics.

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 tool has zero parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description appropriately doesn't add parameter information beyond what's in the schema, maintaining focus on the tool's purpose rather than unnecessary parameter details.

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 clearly states the action ('List') and target resources ('all available skills in the personal and superpowers skill libraries'), making the purpose immediately understandable. It doesn't explicitly differentiate from the sibling tool 'use_skill', but the distinction is implied through the different verbs (list vs use).

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?

The description implies usage context by specifying what skills are listed (personal and superpowers libraries), suggesting this is for discovery rather than application. However, it doesn't provide explicit guidance on when to choose this over 'use_skill' or any prerequisites for accessing these libraries.

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/jmcdice/superpower-mcp'

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