Skip to main content
Glama
LeonNonnast

Dev MCP Prompt Server

by LeonNonnast

list_skills

Retrieve development skills with descriptions and IDs, optionally filtered by tags like clean-code or testing, to identify relevant capabilities for AI-powered development workflows.

Instructions

List all available development skills with descriptions and IDs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoOptional: filter by tags (clean-code, testing, etc.)

Implementation Reference

  • The core handler logic for the 'list_skills' tool within the CallToolRequestSchema switch statement. It retrieves skill prompts from the 'skills' category, optionally filters by tags provided in arguments, maps relevant fields, and returns a formatted JSON list as text content.
    case "list_skills":
      const skillsPrompts =
        await this.promptManager.searchPromptsByCategory("skills");
    
      let skillsList = skillsPrompts.map((skill) => ({
        id: skill.id,
        title: skill.title,
        description: skill.description,
        tags: skill.tags,
        effectiveness: skill.effectiveness,
      }));
    
      if (args && Array.isArray(args.tags) && args.tags.length > 0) {
        const tags: string[] = args.tags;
        skillsList = skillsList.filter((item) => {
          return item.tags.some((item) => tags.includes(item));
        });
      }
    
      logger.info(`Listed ${skillsList.length} skills`);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(skillsList, null, 2),
          },
        ],
      };
  • Helper function in PromptManager used by the list_skills handler to fetch all prompts in the 'skills' category (searchPromptsByCategory('skills')).
    searchPromptsByCategory(category: string) {
      const lowercaseQuery = category.toLowerCase();
      const results: PromptWithScore[] = [];
    
      for (const prompt of this.prompts.values()) {
        let score = 0;
    
        // Check tags
        // Check category
        if (prompt.category.toLowerCase().includes(lowercaseQuery)) {
          score += 1;
        }
    
        if (score > 0) {
          results.push({ ...prompt, searchScore: score });
        }
      }
    
      // Sort by score (descending)
      return results;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a listing operation, implying read-only behavior, but doesn't mention any constraints like rate limits, authentication needs, pagination, or what happens if no skills are found. For a tool with zero annotation coverage, this leaves significant gaps in understanding its operational traits.

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 front-loads the core purpose without any wasted words. It clearly communicates the action, resource, and included details, making it easy to parse quickly.

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?

Given the tool's low complexity (one optional parameter, no output schema, no annotations), the description is adequate but has clear gaps. It covers the basic purpose but lacks behavioral details and usage guidelines. For a simple listing tool, this is the minimum viable level, but it could benefit from more context on when and how to use it 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?

The schema description coverage is 100%, with the single parameter 'tags' documented as optional for filtering by tags like 'clean-code' or 'testing'. The description adds no additional parameter information beyond what the schema provides, such as tag format or examples. Since the schema does the heavy lifting, 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.

Purpose4/5

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

The description clearly states the verb ('List') and resource ('all available development skills'), specifying what information is included ('with descriptions and IDs'). It distinguishes this from siblings like 'load_skills' (which likely loads rather than lists) and 'search_profiles' (which focuses on profiles rather than skills). However, it doesn't explicitly differentiate from 'get_prompt_stats' or 'get_tool_stats', which are about different resources.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to prefer 'list_skills' over 'load_skills' (which might load specific skills) or 'search_profiles' (which might include skill-related searches). There's no context about prerequisites, timing, or exclusions for usage.

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/LeonNonnast/mcpdevprompts'

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