Skip to main content
Glama

brainstorm

Read-only

Apply structured brainstorming frameworks (SCAMPER, Design Thinking) to generate creative ideas with domain context and feasibility analysis.

Instructions

Generate creative ideas using structured frameworks (SCAMPER, Design Thinking, etc.) with domain context, feasibility analysis, and iterative refinement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoGemini model to use. OPTIONS: 'gemini-3-pro-preview' (default, best for creative thinking), 'gemini-3-flash-preview' (faster). Use Pro for complex brainstorming requiring deep domain knowledge. Omit for default.
domainNoDomain expertise to apply. EXAMPLES: 'software', 'business', 'marketing', 'product', 'research', 'healthcare', 'finance'. Helps Gemini apply domain-specific knowledge. Include for specialized output.
promptYesThe brainstorming challenge or question. REQUIRED. Be specific about what you need ideas for (e.g., "ways to reduce API latency", "features for a fitness app", "marketing strategies for B2B SaaS"). More context yields better ideas.
ideaCountNoNumber of ideas to generate. DEFAULT: 12. Use higher (15-20) for exploration, lower (5-8) for focused detailed ideas.
constraintsNoLimitations and requirements to respect. EXAMPLES: 'budget under $10k', 'must work offline', 'launch in 2 weeks'. Helps filter ideas to only feasible options.
methodologyNoBrainstorming framework. OPTIONS: 'auto' (default, AI selects best approach), 'divergent' (maximize quantity of ideas), 'convergent' (refine and prioritize existing ideas), 'scamper' (systematic creative triggers), 'design-thinking' (human-centered solutions), 'lateral' (unexpected connections). Use 'auto' unless you have a specific preference.auto
existingContextNoBackground information to build upon. EXAMPLES: 'we tried X but failed because Y', 'current solution uses React'. Provides context for more relevant ideas.
includeAnalysisNoInclude feasibility/impact/innovation ratings for each idea. DEFAULT: true. Set to false for faster output without analysis.
Behavior4/5

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

Annotations indicate read-only and open-world behavior. The description adds value by specifying that it uses structured frameworks and includes feasibility analysis. No contradiction with annotations; the description enhances understanding beyond the structured fields.

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 conveys the core functionality without unnecessary words. It is appropriately front-loaded with the key action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

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

Given the complexity (8 parameters, no output schema), the description provides a high-level summary of capabilities including domain context, feasibility analysis, and iterative refinement. It covers the essential aspects, though return values are not detailed.

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%, with each parameter well-documented. The description does not add significant extra meaning beyond the schema. Baseline 3 is appropriate given the high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: generating creative ideas using structured frameworks like SCAMPER and Design Thinking, with domain context and analysis. It distinguishes from sibling tools like web-search (factual retrieval) and analyze-media (media analysis) by focusing on ideation.

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 use for creative ideation but does not explicitly state when not to use it or mention alternatives. Given sibling tools for other tasks, more explicit guidance would improve clarity.

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/tuannvm/gemini-mcp-server'

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