Skip to main content
Glama
danielrosehill

Daniel Rosehill's MCP Installer

list_mcps

Discover available MCP servers in the registry, filter by category, or view essential options for installation across multiple development clients.

Instructions

List all available MCPs in the registry. Can filter by category or show only essential MCPs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by category (e.g., "Audio", "Development", "MCP Management")
essential_onlyNoOnly show MCPs marked as essential

Implementation Reference

  • Executes the list_mcps tool by calling the helper listMcps function with input arguments, formatting the MCP list with additional computed fields like requires_secrets, and returning formatted JSON as text content.
    case 'list_mcps': {
      const mcps = await listMcps({
        category: args?.category as string | undefined,
        essentialOnly: args?.essential_only as boolean | undefined
      });
    
      const formatted = mcps.map(mcp => ({
        id: mcp.id,
        name: mcp.name,
        description: mcp.description,
        category: mcp.category,
        type: mcp.type,
        essential: mcp.essential || false,
        requires_secrets: (mcp.secrets?.length || 0) > 0,
        secret_keys: mcp.secrets?.map(s => s.key) || []
      }));
    
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            count: formatted.length,
            mcps: formatted
          }, null, 2)
        }]
      };
    }
  • JSON Schema for the input parameters of the list_mcps tool, defining optional category filter and essential_only boolean flag.
    {
      name: 'list_mcps',
      description: 'List all available MCPs in the registry. Can filter by category or show only essential MCPs.',
      inputSchema: {
        type: 'object',
        properties: {
          category: {
            type: 'string',
            description: 'Filter by category (e.g., "Audio", "Development", "MCP Management")'
          },
          essential_only: {
            type: 'boolean',
            description: 'Only show MCPs marked as essential',
            default: false
          }
        }
      }
  • src/index.ts:176-178 (registration)
    Registers the list_mcps tool (and others) with the MCP server by providing the tools list in response to ListToolsRequestSchema.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools
    }));
  • Helper function listMcps that retrieves the MCP registry and applies filters based on category, essentialOnly, and enabledOnly options before returning the filtered list of MCP entries.
    export async function listMcps(options?: {
      category?: string;
      essentialOnly?: boolean;
      enabledOnly?: boolean;
    }): Promise<McpEntry[]> {
      const registry = await getRegistry();
      let mcps = registry.mcps;
    
      if (options?.category) {
        mcps = mcps.filter(mcp => mcp.category?.toLowerCase() === options.category?.toLowerCase());
      }
    
      if (options?.essentialOnly) {
        mcps = mcps.filter(mcp => mcp.essential === true);
      }
    
      if (options?.enabledOnly !== false) {
        mcps = mcps.filter(mcp => mcp.enabled !== false);
      }
    
      return mcps;
    }
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 mentions filtering capabilities but doesn't describe key behaviors such as pagination, rate limits, authentication requirements, or what the output format looks like (e.g., list structure, fields included). For a read operation with zero annotation coverage, this leaves significant gaps.

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 ('List all available MCPs in the registry') and succinctly adds filtering options. Every word earns its place with no redundancy or wasted text, 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.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (listing with filters), no annotations, and no output schema, the description is minimally adequate but incomplete. It covers the purpose and basic usage but lacks details on behavioral traits and output format, which are crucial for an agent to use it effectively without trial and error.

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?

Schema description coverage is 100%, so the input schema already fully documents both parameters ('category' and 'essential_only') with clear descriptions. The description adds no additional meaning beyond what the schema provides, such as examples of categories or implications of filtering. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('List') and resource ('all available MCPs in the registry'), making it easy to understand what it does. However, it doesn't explicitly differentiate from sibling tools like 'list_installed' or 'get_info', which might offer similar listing functionality with different scopes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by mentioning filtering options ('by category or show only essential MCPs'), but it doesn't provide explicit guidance on when to use this tool versus alternatives like 'list_installed' or 'get_info'. No exclusions or prerequisites are stated, leaving the agent to infer 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

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/danielrosehill/My-MCP-Installer'

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