Skip to main content
Glama
etheaven
by etheaven

brainstorm

Generate creative ideas using structured frameworks like SCAMPER and design thinking. Provide a challenge and receive a set of ideas with analysis.

Instructions

Brainstorm ideas using OpenAI Codex with structured frameworks (SCAMPER, design-thinking, lateral, etc.). Use when the user wants creative ideation, brainstorming, or idea generation via Codex.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesBrainstorming challenge or question
modelNoModel ID. Recommended order: gpt-5.4 (default), gpt-5.3-codex (coding), gpt-5.2-codex, gpt-5.2, gpt-5.1, gpt-5, gpt-5-mini, gpt-5-nano, gpt-4.1.
reasoningEffortNoReasoning effort: none, minimal, low, medium (default), high, xhigh. Higher = deeper analysis, slower, more expensive.
approvalPolicyNoApproval: never, on-request, on-failure, untrusted
sandboxModeNoAccess: read-only, workspace-write, danger-full-access
fullAutoNoFull automation mode
yoloNo⚠️ Bypass all safety (dangerous)
cdNoWorking directory
methodologyNoFramework: divergent, convergent, scamper, design-thinking, lateral, auto (default)auto
domainNoDomain: software, business, creative, research, product, marketing, etc.
constraintsNoLimitations: budget, time, technical, legal, etc.
existingContextNoBackground info or previous attempts
ideaCountNoNumber of ideas (default: 12, range: 5-30)
includeAnalysisNoInclude feasibility/impact analysis
searchNoEnable web search for research (activates web_search_request feature)
ossNoUse local Ollama server
enableFeaturesNoEnable feature flags
disableFeaturesNoDisable feature flags
Behavior2/5

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

No annotations exist, so the description carries full burden. It fails to disclose behavioral traits such as costs, rate limits, auth requirements, or that it uses an AI model (Codex).

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

Conciseness4/5

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

The description is two sentences and front-loaded with the main purpose. The second sentence is somewhat redundant but not excessively verbose.

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?

The tool has 18 parameters and no output schema, but the description is minimal. It does not explain return values or how to effectively use advanced parameters like methodology, domain, etc.

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% and parameter descriptions in the schema are detailed. The description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 states the tool brainstorms ideas using OpenAI Codex with structured frameworks. It distinguishes from siblings like ask-codex (Q&A) and batch-codex (batch processing).

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

Usage Guidelines4/5

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

The description says to use when the user wants creative ideation, brainstorming, or idea generation via Codex. It provides clear context but lacks explicit when-not-to-use or alternatives.

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/etheaven/codex-mcp-server'

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