Skip to main content
Glama

get-download-stats

Retrieve download statistics for top agents from Claude Agents Power. Input a limit to display results, aiding in informed decision-making for team composition and task efficiency.

Instructions

Get download statistics for agents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of top agents to show

Implementation Reference

  • The core handler function that returns a copy of the Map tracking download counts for each agent fetched from GitHub.
    getDownloadStats(): Map<string, number> {
      return new Map(this.downloadStats);
    }
  • Proxy method in AgentManager that delegates download stats retrieval to GitHubIntegration.
    getDownloadStats(): Map<string, number> {
      return this.githubIntegration.getDownloadStats();
    }
  • Helper method that returns the top most downloaded agents, used by the stats functionality.
    getMostDownloadedAgents(limit: number = 10): Array<{name: string, downloads: number}> {
      return this.githubIntegration.getMostDownloaded(limit);
    }
  • MCP tool handler for 'manage-agents' tool with 'stats' action, which retrieves and returns download statistics.
      const stats = agentManager.getMostDownloadedAgents(limit);
      
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              success: true,
              stats,
              message: `Top ${limit} most downloaded agents`,
            }, null, 2),
          },
        ],
      };
    }
  • Input schema definition for the 'manage-agents' MCP tool, which includes 'stats' action for retrieving download statistics.
      name: 'manage-agents',
      description: 'Install agents, get stats, or refresh from GitHub',
      inputSchema: {
        type: 'object',
        properties: {
          action: {
            type: 'string',
            description: 'Management action to perform',
            enum: ['install', 'stats', 'refresh', 'version'],
          },
          agentNames: {
            type: 'array',
            items: { type: 'string' },
            description: 'Agent names to install (for install action)',
          },
          targetPath: {
            type: 'string',
            description: 'Target directory for installation (for install action)',
          },
          language: {
            type: 'string',
            description: 'Language preference for agents',
            enum: ['en', 'ko', 'ja', 'zh'],
            default: 'en',
          },
          limit: {
            type: 'number',
            description: 'Number of top agents to show in stats',
            default: 10,
          },
        },
        required: ['action'],
      },
    },
Behavior2/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. It states the tool's function but lacks critical details such as whether it requires authentication, has rate limits, returns paginated results, or what format the statistics are in (e.g., counts, trends). This leaves significant gaps for an agent to understand how to interact with it effectively.

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 redundant or unnecessary words. It is appropriately sized and front-loaded, making it easy for an agent 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 the lack of annotations and output schema, the description is incomplete. It doesn't explain what the download statistics include (e.g., time ranges, metrics), how results are structured, or any behavioral traits like error handling. For a tool with no structured output information, more context is needed to guide the agent fully.

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 'limit' parameter clearly documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, such as explaining what 'download statistics' entail or how the limit affects ranking. This meets the baseline for high schema coverage.

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 ('Get download statistics') and the resource ('for agents'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'get-agent-details' or 'list-agents' that might also provide agent-related information, preventing 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. For example, it doesn't specify if this is for aggregated stats versus detailed per-agent data, or how it differs from siblings like 'get-agent-details' or 'list-agents', leaving the agent to infer usage context.

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

Related 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/hongsw/claude-agents-power-mcp-server'

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