Skip to main content
Glama
launchframe-dev

LaunchFrame MCP

cli_module_list

List available modules for a LaunchFrame project to identify components like feature-flags or multi-tenancy that can be added to enhance functionality.

Instructions

List all available modules that can be added to a LaunchFrame project (e.g., feature-flags, multi-tenancy).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYesAbsolute path to the LaunchFrame project root

Implementation Reference

  • The handler function for the 'cli_module_list' tool, which executes 'launchframe module:list' within the specified project path using execSync.
    async ({ projectPath }) => {
      try {
        const output = execSync('launchframe module:list', { cwd: projectPath, encoding: 'utf8' });
        return { content: [{ type: 'text', text: output || '(no output)' }] };
      } catch (error: any) {
        return { content: [{ type: 'text', text: error.message }] };
      }
    }
  • The MCP tool registration for 'cli_module_list', including its description, input schema (projectPath), and the handler function definition.
    server.tool(
      'cli_module_list',
      'List all available modules that can be added to a LaunchFrame project (e.g., feature-flags, multi-tenancy).',
      {
        projectPath: z.string().describe('Absolute path to the LaunchFrame project root'),
      },
      async ({ projectPath }) => {
        try {
          const output = execSync('launchframe module:list', { cwd: projectPath, encoding: 'utf8' });
          return { content: [{ type: 'text', text: output || '(no output)' }] };
        } catch (error: any) {
          return { content: [{ type: 'text', text: error.message }] };
        }
      }
    );
Behavior2/5

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

No annotations provided, so description carries full burden. States what is listed but omits output format, pagination behavior, side effects, or error conditions for invalid projectPath.

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?

Single sentence front-loaded with action and resource. Parenthetical examples add value without verbosity. No redundant or wasted text.

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?

Adequate for a single-parameter tool but lacks output description given no output schema exists. Module examples partially compensate for missing return value documentation, but gap remains for programmatic consumption.

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 coverage is 100% with projectPath fully described in schema. Description adds no parameter details, but baseline of 3 applies per rules 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?

Clear verb 'List' and resource 'available modules' with scope 'LaunchFrame project'. Examples clarify module types. Lacks explicit differentiation from sibling cli_module_add (which adds modules vs listing installable candidates).

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?

Provides examples of modules (feature-flags, multi-tenancy) but lacks explicit when-to-use guidance or contrast with cli_module_add or cli_service_list. No prerequisites mentioned despite requiring projectPath.

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/launchframe-dev/mcp'

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