Skip to main content
Glama
LeonNonnast

Dev MCP Prompt Server

by LeonNonnast

search_profiles

Find development profiles by searching through curated prompts for UI/UX design, project setup, and debugging tasks to enhance AI-powered workflows.

Instructions

Search for profiles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'search_profiles' tool: searches for prompts with the 'profile' tag using PromptManager and returns a JSON-formatted list of matching prompts.
    case "search_profiles":
      const profilePrompts = await this.promptManager.searchPromptsByTag(
        "profile"
      );
      logger.info(
        `Search results for "profile" in tags: ${profilePrompts.length} prompts`
      );
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(profilePrompts, null, 2),
          },
        ],
      };
  • Helper function searchPromptsByTag in PromptManager class that implements the tag-based search logic used by the search_profiles tool handler.
    async searchPromptsByTag(tag: string): Promise<PromptWithScore[]> {
      const lowercaseQuery = tag.toLowerCase();
      const results: PromptWithScore[] = [];
    
      for (const prompt of this.prompts.values()) {
        let score = 0;
    
        // Check tags
        if (
          prompt.tags &&
          prompt.tags.some((tag) => tag.toLowerCase().includes(lowercaseQuery))
        ) {
          score += 1;
        }
    
        if (score > 0) {
          results.push({ ...prompt, searchScore: score });
        }
      }
    
      // Sort by score (descending)
      return results;
    }
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. 'Search for profiles' gives no information about traits like read-only vs. destructive, authentication needs, rate limits, pagination, or response format. It lacks any context beyond the basic action, making it inadequate 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 extremely concise with just three words, front-loading the core action and resource without any waste. Every word ('Search for profiles') directly contributes to the purpose, making it efficient and well-structured for its minimal content.

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 lack of annotations and output schema, the description is incomplete. It does not explain what 'profiles' entail, how results are returned, or any behavioral aspects like search scope or limitations. For a search tool with no structured data support, more context is needed to guide effective use.

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% description coverage, meaning no parameters need documentation. The description does not add parameter details, which is acceptable since there are none to explain. It avoids redundancy and appropriately handles the lack of parameters, though it could briefly note the absence of filters or criteria.

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 'Search for profiles' states a clear verb ('Search') and resource ('profiles'), establishing the basic purpose. However, it lacks specificity about what profiles are (e.g., user profiles, skill profiles) and does not differentiate from sibling tools like 'search_prompts' or 'list_skills', leaving ambiguity about scope. It avoids tautology by not merely restating the name, but remains vague.

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 does not mention context, prerequisites, or exclusions, and fails to reference sibling tools such as 'search_prompts' for similar search operations. Usage is implied only by the verb 'Search', but without explicit when/when-not instructions or named alternatives.

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