Skip to main content
Glama
LeonNonnast

Dev MCP Prompt Server

by LeonNonnast

get_tool_stats

Retrieve usage statistics for development prompts to monitor tool performance and optimize AI-powered workflows.

Instructions

Get statistics about available tools

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'get_tool_stats' tool call. It invokes toolManager.getStats() and returns the statistics as JSON text content.
    case "get_tool_stats":
      const toolStats = this.toolManager.getStats();
      logger.info("Retrieved tool statistics");
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(toolStats, null, 2),
          },
        ],
      };
  • Core implementation of tool statistics computation, returning the total number of loaded tools.
    getStats(): ToolsStats {
      const stats: ToolsStats = {
        totalTools: this.tools.size,
      };
    
      return stats;
    }
  • TypeScript interface defining the structure of tool statistics (output schema).
    export interface ToolsStats {
      totalTools: number;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits like rate limits, authentication needs, response format, or whether it's read-only/destructive. It adds minimal context beyond the obvious purpose.

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 no wasted words, front-loading the core purpose. It's appropriately sized for a simple tool with no parameters, making it easy to parse quickly.

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 no annotations, no output schema, and a vague purpose, the description is incomplete. It doesn't explain what 'statistics' includes, how results are structured, or any operational constraints, leaving significant gaps for an agent to understand the tool's behavior fully.

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 no parameter information is needed. The description doesn't add param semantics, but this is acceptable given the lack of parameters, aligning with the baseline for zero-param tools.

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 'Get statistics about available tools' clearly states the action (get) and resource (statistics about tools), but it's vague about what 'statistics' entails and doesn't differentiate from siblings like 'get_prompt_stats' or 'list_skills'. It avoids tautology but lacks specificity.

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 such as 'get_prompt_stats' or 'list_skills'. The description implies usage for statistical queries but offers no context on prerequisites, exclusions, or comparative scenarios with sibling tools.

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