Skip to main content
Glama

notes_insight

Analyze notes using TRILEMMA-PRINCIPLES framework with AI summarization to generate topic insights from Obsidian knowledge bases.

Instructions

Generate insights about a topic using TRILEMMA-PRINCIPLES framework with AI-powered summarization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesTopic keyword or phrase to analyze
maxNotesNoMaximum number of notes to analyze (default: 5)
maxContextLengthNoMaximum context length in characters (default: 50000)
enableSummaryNoWhether to enable AI summarization for long notes (default: true)

Implementation Reference

  • Main handler for 'notes_insight' tool: searches vault for topic-related notes, selects top relevant ones, processes/summarizes content, generates TRILEMMA-PRINCIPLES insights.
    private async handleNotesInsight(args: any) {
      if (!args?.topic) {
        throw new Error('Topic is required');
      }
      
      const topic = args.topic;
      const maxNotes = args.maxNotes || 5;
      const maxContextLength = args.maxContextLength || 50000;
      const enableSummary = args.enableSummary !== undefined ? args.enableSummary : true;
      
      try {
        // Step 1: Search for relevant notes
        const searchResults = await this.searchVault(topic);
        
        // Step 2: Select most relevant notes
        const selectedNotes = await this.selectMostRelevantNotes(searchResults, maxNotes);
        
        // Step 3: Process notes content with AI summarization if needed
        const processedContent = await this.processNotesContent(
          selectedNotes, 
          maxContextLength, 
          enableSummary
        );
        
        // Step 4: Generate insights using TRILEMMA-PRINCIPLES framework
        const insights = await this.generateInsights(topic, processedContent);
        
        return {
          content: [
            {
              type: 'text',
              text: insights,
            },
          ],
        };
      } catch (error) {
        throw new Error(`Failed to generate insights: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • Input schema definition for the notes_insight tool in the tools list.
    name: 'notes_insight',
    description: 'Generate insights about a topic using TRILEMMA-PRINCIPLES framework with AI-powered summarization',
    inputSchema: {
      type: 'object',
      properties: {
        topic: {
          type: 'string',
          description: 'Topic keyword or phrase to analyze'
        },
        maxNotes: {
          type: 'number',
          description: 'Maximum number of notes to analyze (default: 5)',
          default: 5
        },
        maxContextLength: {
          type: 'number',
          description: 'Maximum context length in characters (default: 50000)',
          default: 50000
        },
        enableSummary: {
          type: 'boolean',
          description: 'Whether to enable AI summarization for long notes (default: true)',
          default: true
        }
      },
      required: ['topic'],
    },
  • src/index.ts:1409-1410 (registration)
    Registration of notes_insight handler in the CallToolRequestSchema switch statement.
      return await this.handleNotesInsight(request.params.arguments);
    default:
  • Helper function loading the core TRILEMMA-PRINCIPLES framework prompt used for insight generation.
      private async loadTrilemmaPrompt(): Promise<string> {
        // Embedded complete TRILEMMA-PRINCIPLES framework prompt
        return `# TRILEMMA-PRINCIPLES Integrated Analysis Framework
    
    ## Your Role
    You are an expert strategic analyst capable of identifying structural constraints and breakthrough solutions. Your mission is to apply this integrated framework that combines the Mundell-Fleming Trilemma approach with First Principles Thinking to analyze complex problems and generate innovative solutions.
    
    ## Analysis Protocol
    
    ### LAYER 1: CONSTRAINT IDENTIFICATION (Trilemma Analysis)
    
    #### Step 1: Extract Core Trilemma Elements
    - Identify the three primary objectives/elements in the given scenario
    - Map the inherent conflicts between these elements
    - Analyze the current system's trade-off choices
    - **Output Format**: "The three conflicting elements are: [A], [B], and [C]"
    
    #### Step 2: Constraint Root Analysis
    Analyze the fundamental sources of constraints:
    - **Technical Constraints**: Current technological limitations
    - **Resource Constraints**: Scarcity of time, capital, human resources
    - **Institutional Constraints**: Legal, cultural, organizational barriers
    - **Physical Constraints**: Natural laws, physical limitations
    - **Output Format**: "The primary constraint sources are..."
    
    #### Step 3: Trade-off Consequence Assessment
    - Analyze short-term and long-term impacts of each trade-off option
    - Identify hidden costs and opportunity costs
    - Evaluate gains and losses for all stakeholders
    - **Output Format**: "If we prioritize [X] over [Y] and [Z], the consequences are..."
    
    ### LAYER 2: ASSUMPTION DECONSTRUCTION (First Principles Analysis)
    
    #### Step 4: Challenge Fundamental Assumptions
    Ask critical questions:
    - Are the preconditions of this trilemma necessarily true?
    - Are there overlooked fourth or fifth variables?
    - Are the definitions of each element too narrow?
    - **Output Format**: "The key assumptions to challenge are..."
    
    #### Step 5: Seek Root Principles
    - What are the essential needs behind each element?
    - Where is the true source of conflict?
    - Is there a more fundamental unifying principle?
    - **Output Format**: "The underlying principles reveal that..."
    
    #### Step 6: Redefine Boundary Conditions
    - Can temporal boundaries be adjusted?
    - Can spatial scope be expanded?
    - Can participating entities be recombined?
    - **Output Format**: "By redefining boundaries, we can..."
    
    ### LAYER 3: BREAKTHROUGH SOLUTION DESIGN
    
    #### Step 7: Dimensional Upgrade
    Explore solutions across multiple dimensions:
    - **Temporal Dimension**: Phase-based implementation to resolve conflicts
    - **Spatial Dimension**: Multi-layered, multi-regional solutions
    - **Entity Dimension**: Collaborative division of objectives
    - **Technological Dimension**: Innovation-driven game-changing approaches
    - **Output Format**: "The dimensional breakthrough opportunities are..."
    
    #### Step 8: New Equilibrium Design
    - Design system architecture that transcends trilemma constraints
    - Build dynamic rather than static balance
    - Create positive-sum rather than zero-sum games
    - **Output Format**: "The new equilibrium model involves..."
    
    #### Step 9: Implementation Pathway
    - Map transition path from current to target state
    - Design risk controls and contingency plans
    - Establish effectiveness evaluation and iteration mechanisms
    - **Output Format**: "The implementation strategy includes..."
    
    ## Analysis Template
    
    For each analysis, structure your response as follows:
    
    ### 🔍 **TRILEMMA IDENTIFICATION**
    [Apply Steps 1-3: Identify constraints and trade-offs]
    
    ### 💭 **FIRST PRINCIPLES QUESTIONING** 
    [Apply Steps 4-6: Challenge assumptions and seek root causes]
    
    ### 🚀 **BREAKTHROUGH SOLUTION**
    [Apply Steps 7-9: Design innovative solutions and implementation paths]
    
    ### 📊 **SYNTHESIS & RECOMMENDATIONS**
    [Provide clear, actionable insights and next steps]
    
    ## Key Principles to Follow
    
    ### Dynamic Thinking
    - Constraints are not permanent
    - Technological progress can change the rules
    - System evolution may create new possibilities
    
    ### Multi-Level Analysis
    - Solutions may exist at different hierarchical levels
    - Micro-constraints ≠ Macro-constraints
    - Short-term conflicts may resolve in long-term
    
    ### Creative Problem-Solving
    - Best solutions often transcend original frameworks
    - Redefining problems is more important than solving them
    - Fourth-dimensional thinking is key to breakthroughs
    
    ## Quality Standards
    
    Your analysis should demonstrate:
    - **Accuracy** in constraint identification
    - **Depth** in assumption questioning  
    - **Creativity** in solution design
    - **Feasibility** in implementation planning
    
    ## Special Instructions
    
    1. **Always start with constraint identification** before jumping to solutions
    2. **Question every assumption explicitly** - don't accept conventional wisdom
    3. **Seek genuine breakthrough** rather than incremental improvements
    4. **Balance creativity with practicality** in your recommendations
    5. **Provide specific, actionable guidance** rather than abstract concepts
    
    Your goal is to help users see beyond apparent limitations and discover innovative pathways that transcend traditional trade-offs.`;
      }
  • Helper that constructs the insight generation prompt using the TRILEMMA framework and processed notes.
      private async generateInsights(topic: string, processedContent: string): Promise<string> {
        // Load the TRILEMMA-PRINCIPLES framework from the prepared file
        const trilemmaPrompt = await this.loadTrilemmaPrompt();
        
        // Construct the final prompt for insights generation
        const insightPrompt = `${trilemmaPrompt}
    
    ## Analysis Context
    
    **Topic**: ${topic}
    
    **Relevant Notes Content**:
    ${processedContent}
    
    ## Task
    
    Apply the TRILEMMA-PRINCIPLES framework to analyze the topic "${topic}" based on the provided notes content. Focus on identifying constraints, challenging assumptions, and proposing breakthrough solutions.
    
    Please provide your analysis following the framework structure:
    1. TRILEMMA IDENTIFICATION
    2. FIRST PRINCIPLES QUESTIONING  
    3. BREAKTHROUGH SOLUTION
    4. SYNTHESIS & RECOMMENDATIONS`;
    
        return insightPrompt;
      }
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. While it mentions 'AI-powered summarization' and the TRILEMMA-PRINCIPLES framework, it doesn't describe what insights are generated, the format of output, potential limitations, or how it interacts with notes (e.g., does it analyze existing notes from the vault?). For a tool with no annotations and no output schema, this leaves significant gaps in understanding its behavior.

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 states the core purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent to quickly understand what the tool does.

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 complexity of generating insights with AI and a specific framework, no annotations, and no output schema, the description is incomplete. It doesn't explain what insights look like, how they're derived, or what the tool returns. This leaves the agent with insufficient context to use the tool effectively beyond basic parameter passing.

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%, so the schema already documents all four parameters thoroughly. The description doesn't add any meaning beyond what the schema provides about parameters like 'topic', 'maxNotes', etc. It implies topic analysis but doesn't elaborate on parameter interactions or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 insights about a topic using TRILEMMA-PRINCIPLES framework with AI-powered summarization.' It specifies the verb ('generate insights'), resource ('topic'), and method ('TRILEMMA-PRINCIPLES framework with AI-powered summarization'). However, it doesn't explicitly distinguish this from sibling tools like 'search_vault' or 'read_note' that might also provide information about topics.

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 doesn't mention prerequisites, ideal use cases, or when to choose this over sibling tools like 'search_vault' or 'read_note' for topic analysis. The agent must infer usage from the purpose alone.

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/newtype-01/obsidian-mcp'

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