Skip to main content
Glama
orzcls

Gemini CLI MCP Server

by orzcls

brainstorm

Generate novel ideas by applying creative frameworks like SCAMPER and Design Thinking, integrating domain context, clustering concepts, analyzing feasibility, and refining iteratively.

Instructions

Generate novel ideas with dynamic context gathering. --> Creative frameworks (SCAMPER, Design Thinking, etc.), domain context integration, idea clustering, feasibility analysis, and iterative refinement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesPrimary brainstorming challenge or question to explore
modelNoOptional model to use (e.g., 'gemini-2.5-flash'). If not specified, uses the default model (gemini-2.5-pro).
methodologyNoBrainstorming framework: 'divergent' (generate many ideas), 'convergent' (refine existing), 'scamper' (systematic triggers), 'design-thinking' (human-centered), 'lateral' (unexpected connections), 'auto' (AI selects best)auto
domainNoDomain context for specialized brainstorming (e.g., 'software', 'business', 'creative', 'research', 'product', 'marketing')
constraintsNoKnown limitations, requirements, or boundaries (budget, time, technical, legal, etc.)
existingContextNoBackground information, previous attempts, or current state to build upon
ideaCountNoTarget number of ideas to generate (default: 10-15)
includeAnalysisNoInclude feasibility, impact, and implementation analysis for generated ideas
powershellPathNoOptional custom PowerShell executable path (e.g., 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe' or 'pwsh'). If not specified, auto-detects available PowerShell.

Implementation Reference

  • Handler function for the 'brainstorm' tool. Destructures arguments, constructs an enhanced brainstorming prompt incorporating user-provided methodology, domain, constraints, existing context, idea count, and analysis preference, then executes Gemini CLI to generate ideas and returns the result.
    case "brainstorm":
        const { 
            prompt: brainstormPrompt, 
            model: brainstormModel, 
            methodology, 
            domain, 
            constraints, 
            existingContext, 
            ideaCount, 
            includeAnalysis,
            powershellPath: brainstormPowershellPath
        } = args;
        
        console.error('[GMCPT] brainstorm tool called with prompt: ' + (brainstormPrompt ? brainstormPrompt.slice(0, 50) + '...' : 'undefined'));
        console.error('[GMCPT] Methodology: ' + methodology + ', Domain: ' + domain);
        
        // Build enhanced brainstorming prompt
        let enhancedPrompt = `BRAINSTORMING SESSION\n\nChallenge: ${brainstormPrompt}\n\n`;
        
        if (methodology && methodology !== 'auto') {
            enhancedPrompt += `Framework: Use ${methodology} methodology for idea generation.\n`;
        }
        
        if (domain) {
            enhancedPrompt += `Domain Context: ${domain}\n`;
        }
        
        if (constraints) {
            enhancedPrompt += `Constraints: ${constraints}\n`;
        }
        
        if (existingContext) {
            enhancedPrompt += `Background: ${existingContext}\n`;
        }
        
        enhancedPrompt += `\nGenerate ${ideaCount || 12} creative and diverse ideas. `;
        
        if (includeAnalysis !== false) {
            enhancedPrompt += `For each idea, provide a brief feasibility assessment and potential impact.`;
        }
        
        const brainstormResult = await executeGeminiCLI(enhancedPrompt, brainstormModel, false, false, brainstormPowershellPath);
        return {
            content: [{
                type: "text",
                text: brainstormResult
            }]
        };
  • Registration of the 'brainstorm' tool in the tools array used by ListToolsRequestSchema handler, including name, description, and complete input schema definition.
    {
        name: "brainstorm",
        description: "Generate novel ideas with dynamic context gathering. --> Creative frameworks (SCAMPER, Design Thinking, etc.), domain context integration, idea clustering, feasibility analysis, and iterative refinement.",
        inputSchema: {
            type: "object",
            properties: {
                prompt: {
                    type: "string",
                    minLength: 1,
                    description: "Primary brainstorming challenge or question to explore"
                },
                model: {
                    type: "string",
                    description: "Optional model to use (e.g., 'gemini-2.5-flash'). If not specified, uses the default model (gemini-2.5-pro)."
                },
                methodology: {
                    type: "string",
                    enum: ["divergent", "convergent", "scamper", "design-thinking", "lateral", "auto"],
                    default: "auto",
                    description: "Brainstorming framework: 'divergent' (generate many ideas), 'convergent' (refine existing), 'scamper' (systematic triggers), 'design-thinking' (human-centered), 'lateral' (unexpected connections), 'auto' (AI selects best)"
                },
                domain: {
                    type: "string",
                    description: "Domain context for specialized brainstorming (e.g., 'software', 'business', 'creative', 'research', 'product', 'marketing')"
                },
                constraints: {
                    type: "string",
                    description: "Known limitations, requirements, or boundaries (budget, time, technical, legal, etc.)"
                },
                existingContext: {
                    type: "string",
                    description: "Background information, previous attempts, or current state to build upon"
                },
                ideaCount: {
                    type: "integer",
                    exclusiveMinimum: 0,
                    default: 12,
                    description: "Target number of ideas to generate (default: 10-15)"
                },
                includeAnalysis: {
                    type: "boolean",
                    default: true,
                    description: "Include feasibility, impact, and implementation analysis for generated ideas"
                },
                powershellPath: {
                    type: "string",
                    description: "Optional custom PowerShell executable path (e.g., 'C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe' or 'pwsh'). If not specified, auto-detects available PowerShell."
                }
            },
            required: ["prompt"]
        }
    },
  • Input schema for the 'brainstorm' tool, defining properties, types, descriptions, defaults, enums, and required fields for validation.
    inputSchema: {
        type: "object",
        properties: {
            prompt: {
                type: "string",
                minLength: 1,
                description: "Primary brainstorming challenge or question to explore"
            },
            model: {
                type: "string",
                description: "Optional model to use (e.g., 'gemini-2.5-flash'). If not specified, uses the default model (gemini-2.5-pro)."
            },
            methodology: {
                type: "string",
                enum: ["divergent", "convergent", "scamper", "design-thinking", "lateral", "auto"],
                default: "auto",
                description: "Brainstorming framework: 'divergent' (generate many ideas), 'convergent' (refine existing), 'scamper' (systematic triggers), 'design-thinking' (human-centered), 'lateral' (unexpected connections), 'auto' (AI selects best)"
            },
            domain: {
                type: "string",
                description: "Domain context for specialized brainstorming (e.g., 'software', 'business', 'creative', 'research', 'product', 'marketing')"
            },
            constraints: {
                type: "string",
                description: "Known limitations, requirements, or boundaries (budget, time, technical, legal, etc.)"
            },
            existingContext: {
                type: "string",
                description: "Background information, previous attempts, or current state to build upon"
            },
            ideaCount: {
                type: "integer",
                exclusiveMinimum: 0,
                default: 12,
                description: "Target number of ideas to generate (default: 10-15)"
            },
            includeAnalysis: {
                type: "boolean",
                default: true,
                description: "Include feasibility, impact, and implementation analysis for generated ideas"
            },
            powershellPath: {
                type: "string",
                description: "Optional custom PowerShell executable path (e.g., 'C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe' or 'pwsh'). If not specified, auto-detects available PowerShell."
            }
        },
        required: ["prompt"]
    }
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. It mentions 'dynamic context gathering,' 'feasibility analysis,' and 'iterative refinement,' which hint at process complexity, but lacks critical details: whether this is a read-only or mutating operation, expected runtime, rate limits, authentication needs, or output format. For a tool with 9 parameters and no annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence fragment followed by a list, which is moderately efficient but lacks clear structure. The list ('Creative frameworks...') is dense and could be better organized. While it avoids redundancy, it doesn't front-load the most critical information, and some phrases like 'dynamic context gathering' are vague without elaboration, reducing overall clarity.

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 tool's complexity (9 parameters, no annotations, no output schema), the description is incomplete. It omits essential context: what the output looks like (e.g., list of ideas, structured analysis), how 'iterative refinement' works in practice, error conditions, or performance expectations. For a brainstorming tool with multiple parameters and no structured output, more guidance is needed to ensure effective use.

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%, so parameters are well-documented in the schema itself. The description adds minimal semantic value beyond the schema—it mentions 'creative frameworks' and 'domain context integration,' which loosely map to the 'methodology' and 'domain' parameters but don't provide additional syntax or usage insights. This meets the baseline for high schema coverage without compensating for gaps.

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: 'Generate novel ideas with dynamic context gathering.' It specifies the verb ('generate') and resource ('novel ideas'), and mentions key capabilities like creative frameworks and analysis. However, it doesn't explicitly differentiate from sibling tools like 'ask-gemini' which might also generate ideas, leaving some ambiguity about when to choose this specific brainstorming tool.

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. It lists capabilities like 'creative frameworks' and 'domain context integration' but doesn't specify scenarios where this tool is preferred over sibling tools (e.g., 'ask-gemini' for general queries). There's no mention of prerequisites, constraints, or comparative use cases, leaving the agent with minimal contextual direction.

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/orzcls/gemini-mcp-tool-windows-fixed'

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