Skip to main content
Glama
MushroomFleet

DeepLucid3D UCPF Server

creative_exploration

Explore diverse perspectives and creative connections on a topic, incorporating metaphors and optional constraints to generate novel insights and solutions.

Instructions

Generate novel perspectives and connections for a topic

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
constraintsNoOptional constraints or parameters to consider
include_metaphorsNoWhether to include metaphorical thinking
perspective_countNoNumber of perspectives to generate
session_idNoOptional session ID for maintaining state between calls
topicYesThe topic or problem to explore creatively

Implementation Reference

  • The core handler function `exploreCreatively` that implements the tool logic: extracts concepts, generates creative perspectives, connections, metaphors using imported patterns, compiles insights, and formats output.
    export async function exploreCreatively(
      topic: string,
      constraints: string[] = [],
      creativePatterns: CreativePatterns,
      ucpfCore: UcpfCore,
      stateManager: StateManager,
      sessionId?: string,
      options: ExplorationOptions = {}
    ): Promise<string> {
      // Set defaults for options
      const { 
        perspectiveCount = 3,
        connectionCount = 3,
        metaphorCount = 3,
        includeMetaphors = true,
        focusAreas = []
      } = options;
    
      // Extract concepts from the topic and constraints
      const topicWords = topic.split(' ');
      const constraintWords = constraints.join(' ').split(' ');
      const allWords = [...topicWords, ...constraintWords];
      
      // Filter for potential concepts (words longer than 3 characters)
      const concepts = Array.from(new Set(
        allWords
          .filter(word => word.length > 3)
          .map(word => word.replace(/[^\w]/g, ''))
          .filter(word => word.length > 0)
      ));
    
      // Generate perspectives, connections, and metaphors
      const perspectives = creativePatterns.generatePerspectives(
        topic, perspectiveCount
      );
      
      const connections = creativePatterns.generateConnections(
        concepts, connectionCount
      );
      
      const metaphors = includeMetaphors ? 
        creativePatterns.generateMetaphors(topic, metaphorCount) : [];
    
      // Generate some insights based on all of the above
      const insights = [
        "Consider combining elements from different perspectives to create hybrid solutions",
        "Look for patterns that emerge across the different viewpoints",
        "Challenge your initial assumptions about the constraints of the problem"
      ];
    
      // Construct the result
      const result: ExplorationResult = {
        perspectives,
        connections,
        metaphors,
        insights
      };
      
      // Format and return the results
      return formatExploration(result);
    }
  • MCP input schema for the 'creative_exploration' tool defining required 'topic' and optional parameters like constraints, perspective_count, include_metaphors, session_id.
    inputSchema: {
      type: "object",
      properties: {
        topic: {
          type: "string",
          description: "The topic or problem to explore creatively"
        },
        constraints: {
          type: "array",
          items: {
            type: "string"
          },
          description: "Optional constraints or parameters to consider"
        },
        perspective_count: {
          type: "number",
          description: "Number of perspectives to generate",
          default: 3
        },
        include_metaphors: {
          type: "boolean",
          description: "Whether to include metaphorical thinking",
          default: true
        },
        session_id: {
          type: "string",
          description: "Optional session ID for maintaining state between calls"
        }
      },
      required: ["topic"]
    }
  • src/index.ts:364-398 (registration)
    Registration of the 'creative_exploration' tool in the MCP server's ListToolsRequestSchema handler, including name, description, and input schema.
    {
      name: "creative_exploration",
      description: "Generate novel perspectives and connections for a topic",
      inputSchema: {
        type: "object",
        properties: {
          topic: {
            type: "string",
            description: "The topic or problem to explore creatively"
          },
          constraints: {
            type: "array",
            items: {
              type: "string"
            },
            description: "Optional constraints or parameters to consider"
          },
          perspective_count: {
            type: "number",
            description: "Number of perspectives to generate",
            default: 3
          },
          include_metaphors: {
            type: "boolean",
            description: "Whether to include metaphorical thinking",
            default: true
          },
          session_id: {
            type: "string",
            description: "Optional session ID for maintaining state between calls"
          }
        },
        required: ["topic"]
      }
    },
  • src/index.ts:478-517 (registration)
    Dispatch handler in CallToolRequestSchema that validates inputs, prepares options, calls exploreCreatively, and returns MCP-formatted response.
    case "creative_exploration": {
      // Validate required parameters
      if (!args?.topic || typeof args.topic !== "string") {
        throw new McpError(
          ErrorCode.InvalidParams,
          "Required parameter 'topic' must be a string"
        );
      }
      
      // Optional parameters
      const constraints = Array.isArray(args.constraints) ? 
        args.constraints.map(String) : [];
      const perspectiveCount = typeof args.perspective_count === "number" ?
        Math.max(1, Math.min(5, args.perspective_count)) : 3;
      const includeMetaphors = args.include_metaphors !== false;
      const sessionId = args.session_id as string | undefined;
      
      // Process the creative exploration
      const results = await exploreCreatively(
        args.topic,
        constraints,
        creativePatterns,
        ucpfCore,
        stateManager,
        sessionId,
        {
          perspectiveCount,
          includeMetaphors
        }
      );
      
      return {
        content: [
          {
            type: "text",
            text: results
          }
        ]
      };
    }
  • Supporting function to format ExplorationResult into structured Markdown output with sections for perspectives, connections, metaphors, and key insights.
    export function formatExploration(result: ExplorationResult): string {
      const formatSection = (title: string, content: string): string => {
        return `## ${title}\n\n${content}\n\n`;
      };
    
      let output = "";
    
      // Format perspectives
      if (result.perspectives.length > 0) {
        output += formatSection("Alternative Perspectives",
          result.perspectives
            .map(p => (
              `### ${p.viewpoint}\n` +
              `**Rationale:** ${p.rationale}\n` +
              (p.implications.length > 0 ? 
                "**Implications:**\n" + p.implications.map(i => `- ${i}`).join("\n") : 
                "") +
              (p.limitingBeliefs.length > 0 ? 
                "\n\n**Limiting Beliefs to Challenge:**\n" + p.limitingBeliefs.map(b => `- ${b}`).join("\n") : 
                "") +
              (p.potentialOutcomes.length > 0 ? 
                "\n\n**Potential Outcomes:**\n" + p.potentialOutcomes.map(o => `- ${o}`).join("\n") : 
                "")
            ))
            .join("\n\n")
        );
      }
    
      // Format connections
      if (result.connections.length > 0) {
        output += formatSection("Creative Connections",
          result.connections
            .map(c => (
              `### ${c.type.charAt(0).toUpperCase() + c.type.slice(1)}: ${c.source} ↔ ${c.target}\n` +
              `${c.description}\n\n` +
              `**Insight:** ${c.insight}`
            ))
            .join("\n\n")
        );
      }
    
      // Format metaphors
      if (result.metaphors.length > 0) {
        output += formatSection("Metaphorical Thinking",
          "Consider these metaphors to spark new insights:\n\n" +
          result.metaphors.map(m => `- ${m}`).join("\n")
        );
      }
    
      // Format insights
      if (result.insights.length > 0) {
        output += formatSection("Key Insights",
          result.insights.map(i => `- ${i}`).join("\n")
        );
      }
    
      return output;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions generating 'novel perspectives and connections,' which implies a creative, non-destructive process, but fails to detail aspects like rate limits, authentication needs, output format, or whether it maintains state (e.g., via session_id). For a tool with no annotations, this is a significant gap in transparency.

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: 'Generate novel perspectives and connections for a topic.' It is front-loaded with the core action and resource, with no wasted words. This makes it easy to parse and understand quickly.

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 (5 parameters, no output schema, no annotations), the description is incomplete. It lacks details on behavioral traits, output format, and how parameters interact, which are crucial for an AI agent to use it effectively. Without annotations or an output schema, the description should provide more context to compensate, but it does not.

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%, meaning all parameters are documented in the schema. The description adds no additional meaning beyond what the schema provides, such as explaining how 'constraints' affect generation or what 'perspective_count' entails. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 function: 'Generate novel perspectives and connections for a topic.' It specifies the verb ('generate') and resource ('perspectives and connections'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'analyze_problem' or 'manage_state', which might also involve topic exploration or state management.

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. There is no mention of when to choose 'creative_exploration' over 'analyze_problem' or 'manage_state', nor any context about prerequisites or exclusions. This leaves the agent without clear usage instructions.

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

Related 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/MushroomFleet/DeepLucid3D-MCP'

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