Skip to main content
Glama

brainstorm_enhancements

Generate creative ideas to improve concepts, products, or features by focusing on innovation, feasibility, and user value.

Instructions

Generates creative ideas for improving a given concept, product, or feature, focusing on innovation, feasibility, and user value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conceptYesA description of the concept, product, or feature to enhance

Implementation Reference

  • The main handler function that implements the core logic of the 'brainstorm_enhancements' tool. It handles input validation, rate limiting, prompt generation using predefined templates, makes an API call to Deepseek, and formats the response.
    export async function handler(args: unknown): Promise<ToolResponse> {
      // Check rate limit first
      if (!checkRateLimit()) {
        return {
          content: [
            {
              type: 'text',
              text: 'Rate limit exceeded. Please try again later.',
            },
          ],
          isError: true,
        };
      }
    
      // Validate arguments
      if (!args || typeof args !== 'object') {
        return {
          content: [
            {
              type: 'text',
              text: 'Invalid arguments provided.',
            },
          ],
          isError: true,
        };
      }
    
      try {
        // Type guard for BrainstormEnhancementsArgs
        if (!('concept' in args) || typeof args.concept !== 'string') {
          return {
            content: [
              {
                type: 'text',
                text: 'Concept parameter is required and must be a string.',
              },
            ],
            isError: true,
          };
        }
    
        const typedArgs = args as BrainstormEnhancementsArgs;
    
        // Sanitize input
        const sanitizedConcept = sanitizeInput(typedArgs.concept);
    
        // Create the complete prompt
        const prompt = createPrompt(PROMPT_TEMPLATE, {
          concept: sanitizedConcept,
        });
    
        // Make the API call
        const response = await makeDeepseekAPICall(prompt, SYSTEM_PROMPT);
    
        if (response.isError) {
          return {
            content: [
              {
                type: 'text',
                text: `Error generating enhancement ideas: ${response.errorMessage || 'Unknown error'}`,
              },
            ],
            isError: true,
          };
        }
    
        // Return the formatted response
        return {
          content: [
            {
              type: 'text',
              text: response.text,
            },
          ],
        };
      } catch (error) {
        console.error('Brainstorm enhancements tool error:', error);
        return {
          content: [
            {
              type: 'text',
              text: `Error processing enhancement ideas: ${error instanceof Error ? error.message : 'Unknown error'}`,
            },
          ],
          isError: true,
        };
      }
    }
  • The ToolDefinition object defining the tool's name, description, and input schema (requires 'concept' string).
    export const definition: ToolDefinition = {
      name: 'brainstorm_enhancements',
      description: 'Generates creative ideas for improving a given concept, product, or feature, focusing on innovation, feasibility, and user value.',
      inputSchema: {
        type: 'object',
        properties: {
          concept: {
            type: 'string',
            description: 'A description of the concept, product, or feature to enhance',
          },
        },
        required: ['concept'],
      },
    };
  • TypeScript interface defining the expected input arguments for the tool.
    export interface BrainstormEnhancementsArgs {
      concept: string;
    }
  • src/server.ts:56-64 (registration)
    Registers the tool's definition in the listTools handler, making it discoverable by clients.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        secondOpinion.definition,
        codeReview.definition,
        designCritique.definition,
        writingFeedback.definition,
        brainstormEnhancements.definition,
      ],
    }));
  • src/server.ts:125-134 (registration)
    Handles incoming callTool requests for 'brainstorm_enhancements' by validating args and invoking the tool handler.
    case "brainstorm_enhancements": {
      if (!isBrainstormEnhancementsArgs(args)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          "Invalid parameters for brainstorm enhancements"
        );
      }
      response = await brainstormEnhancements.handler(args);
      break;
    }
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 the tool 'generates' ideas and focuses on certain criteria, but doesn't describe output format, potential limitations (e.g., idea count, quality), or any side effects like rate limits or authentication needs. This leaves significant gaps for a tool that produces creative content.

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 action and purpose without any wasted words. Every part of the sentence contributes to understanding the tool's function and focus areas.

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 lack of annotations and output schema, the description is incomplete for a creative generation tool. It doesn't explain what the output looks like (e.g., list of ideas, structured format), how many ideas are generated, or any behavioral constraints, leaving the agent with insufficient context for 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%, with the single parameter 'concept' well-documented in the schema. The description adds marginal value by reiterating that the concept is for 'enhancing' and specifying it can be a 'concept, product, or feature', but doesn't provide additional syntax or format details beyond what the schema already covers.

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 specific verbs ('Generates creative ideas for improving') and resources ('concept, product, or feature'), and specifies the focus areas ('innovation, feasibility, and user value'). However, it doesn't explicitly differentiate from sibling tools like 'design_critique' or 'second_opinion', which might also involve improvement suggestions.

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 like 'design_critique' or 'second_opinion', nor does it mention any prerequisites or exclusions. It implies usage for enhancement ideas but lacks explicit context for tool selection.

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/cyanheads/mentor-mcp-server'

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