Skip to main content
Glama

memory_intelligent_analysis

Analyze project documentation to identify patterns, generate predictions, and provide actionable recommendations for improvement.

Instructions

Get intelligent analysis with patterns, predictions, and recommendations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYesPath to the project for analysis
baseAnalysisYesBase analysis data to enhance

Implementation Reference

  • The core handler function for the memory_intelligent_analysis tool. It enhances base analysis with project history, similar projects, extracted patterns, and recommendations using the memory system, then stores the enhanced analysis.
    export async function handleMemoryIntelligentAnalysis(args: {
      projectPath: string;
      baseAnalysis: any;
    }): Promise<any> {
      await initializeMemory();
    
      // Get project history and similar projects for enhanced analysis
      const projectId = args.baseAnalysis.projectId || args.projectPath;
      const history = await recallProjectHistory(projectId);
      const similarProjects = await getSimilarProjects(args.baseAnalysis);
    
      // Enhance analysis with memory insights
      const enhancedAnalysis = {
        ...args.baseAnalysis,
        memoryInsights: {
          projectHistory: history,
          similarProjects,
          patterns: await extractPatterns(args.baseAnalysis, history.history),
          recommendations: await generateRecommendations(
            args.baseAnalysis,
            similarProjects,
          ),
        },
      };
    
      // Remember this enhanced analysis
      await rememberAnalysis(args.projectPath, enhancedAnalysis);
    
      return enhancedAnalysis;
    }
  • Registration of the memory_intelligent_analysis tool in the memoryTools array, including name, description, and input schema.
    {
      name: "memory_intelligent_analysis",
      description:
        "Get intelligent analysis with patterns, predictions, and recommendations",
      inputSchema: {
        type: "object",
        properties: {
          projectPath: {
            type: "string",
            description: "Path to the project for analysis",
          },
          baseAnalysis: {
            type: "object",
            description: "Base analysis data to enhance",
          },
        },
        required: ["projectPath", "baseAnalysis"],
      },
    },
  • Input schema definition for the memory_intelligent_analysis tool, specifying required projectPath and baseAnalysis parameters.
      type: "object",
      properties: {
        projectPath: {
          type: "string",
          description: "Path to the project for analysis",
        },
        baseAnalysis: {
          type: "object",
          description: "Base analysis data to enhance",
        },
      },
      required: ["projectPath", "baseAnalysis"],
    },
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. It mentions 'Get intelligent analysis' but does not disclose behavioral traits such as whether this is a read-only operation, if it requires specific permissions, its computational cost, rate limits, or what the output format might be. For a tool with no annotations, 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.

Conciseness4/5

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

The description is a single, efficient sentence that is front-loaded with the main action ('Get intelligent analysis'). It avoids unnecessary words, but could be more structured by specifying the resource or domain to improve clarity without adding bulk.

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 implied by 'intelligent analysis' and the lack of annotations and output schema, the description is incomplete. It does not explain what the analysis covers, how results are returned, or any limitations, making it inadequate for a tool with two parameters and no structured output information.

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 both parameters ('projectPath' and 'baseAnalysis'). The description does not add any meaning beyond what the schema provides, such as explaining how 'baseAnalysis' enhances the analysis or what 'intelligent analysis' entails. Baseline 3 is appropriate when schema does the heavy lifting.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'Get intelligent analysis with patterns, predictions, and recommendations' which provides a general purpose (analysis with specific outputs) but is vague about what exactly is being analyzed. It mentions 'patterns, predictions, and recommendations' but doesn't specify the domain or resource clearly, making it less distinct from sibling tools like 'analyze_repository' or 'memory_insights'.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions, and with many sibling tools (e.g., 'analyze_repository', 'memory_insights'), there is no indication of how this differs or when it is preferred, leaving usage unclear.

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/tosin2013/documcp'

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