Skip to main content
Glama
LeonNonnast

Dev MCP Prompt Server

by LeonNonnast

get_prompt_stats

Retrieve statistics about available development prompts to analyze usage patterns and optimize AI-powered workflows.

Instructions

Get statistics about available prompts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'get_prompt_stats' tool: retrieves statistics from PromptManager and returns them as JSON text content.
    case "get_prompt_stats":
      const promptStats = this.promptManager.getStats();
      logger.info("Retrieved prompt statistics");
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(promptStats, null, 2),
          },
        ],
      };
  • The getStats() method in PromptManager that computes and returns prompt statistics: total prompts, number of categories, and breakdown by category.
    getStats(): PromptStats {
      const stats: PromptStats = {
        totalPrompts: this.prompts.size,
        categories: this.categories.size,
        categoryBreakdown: {},
      };
    
      for (const category of this.categories) {
        stats.categoryBreakdown[category] = Array.from(
          this.prompts.values()
        ).filter((prompt) => prompt.category === category).length;
      }
    
      return stats;
    }
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 but only states the action without details on permissions, rate limits, response format, or side effects. It doesn't clarify if this is a read-only operation or has other behavioral traits, making it insufficient for informed use.

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 directly states the tool's purpose without any unnecessary words or structural fluff. It is front-loaded and appropriately sized for a simple tool, making it highly concise and well-structured.

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 for a tool that likely returns statistical data. It doesn't explain what statistics are provided, the format of the response, or any prerequisites, leaving significant gaps in understanding the tool's full context.

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 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter details, and it appropriately avoids redundancy, earning a high baseline score for this context.

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 tool's purpose with a specific verb ('Get') and resource ('statistics about available prompts'), making it easy to understand what the tool does. However, it doesn't differentiate from sibling tools like 'search_prompts' or 'get_tool_stats', which prevents a perfect score.

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 like 'search_prompts' or 'get_tool_stats'. It lacks context about whether this is for aggregated data, metadata, or other specific use cases, leaving the agent without clear usage instructions.

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