Skip to main content
Glama
nicavcrm

Memory Bank MCP Server

by nicavcrm

VAN Mode

van_mode

Analyze project complexity and initialize tasks for structured workflow management using the Memory Bank system, enabling efficient project planning and execution.

Instructions

Initialize project and determine complexity level. Entry point for the Memory Bank system.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
complexityYes
task_descriptionNo

Implementation Reference

  • Core execution logic of the van_mode tool: initializes Memory Bank system by generating and storing project template and active context based on complexity level and task description, determines next mode, and returns success response.
        handler: async (input: VanModeInput): Promise<ToolResponse> => {
          const timestamp = new Date().toISOString();
          const template = `# Memory Bank System
    
    ## Project Overview
    - **Complexity Level**: ${input.complexity}
    - **Task**: ${input.task_description || 'Task description pending'}
    - **Initialized**: ${timestamp}
    
    ## Status
    - [ ] VAN Mode: Project initialization
    - [ ] PLAN Mode: Implementation planning
    - [ ] CREATIVE Mode: Design decisions (if required)
    - [ ] IMPLEMENT Mode: Code implementation
    - [ ] REFLECT+ARCHIVE Mode: Completion and documentation
    
    ## Current Phase: VAN
    **Next Steps**: ${input.complexity === '1' ? 'Proceed directly to IMPLEMENT mode' : 'Move to PLAN mode for detailed planning'}
    
    ## Memory Bank Files
    - tasks.md: ✅ Initialized
    - activeContext.md: Pending
    - progress.md: Pending
    - implementation-plan.md: Pending
    `;
    
          this.storage.setTasks(template);
    
          const activeContext = `# Active Context
    
    ## Current Task
    ${input.task_description || 'Task description pending'}
    
    ## Complexity Level: ${input.complexity}
    ${this.getComplexityDescription(input.complexity)}
    
    ## Current Mode: VAN
    - Status: Completed
    - Next Mode: ${input.complexity === '1' ? 'IMPLEMENT' : 'PLAN'}
    `;
    
          this.storage.setActiveContext(activeContext);
    
          return {
            content: [{
              type: 'text',
              text: `✅ VAN Mode initialized successfully!\n\n**Project Complexity**: Level ${input.complexity}\n**Next Mode**: ${input.complexity === '1' ? 'IMPLEMENT (direct implementation)' : 'PLAN (detailed planning required)'}\n\nMemory Bank files have been created and the project structure is ready.`
            }]
          };
        }
  • src/server.ts:22-37 (registration)
    MCP server registration of the 'van_mode' tool, providing Zod-validated input schema and delegating execution to the underlying tool handler.
    this.server.registerTool(
      'van_mode',
      {
        title: 'VAN Mode',
        description: 'Initialize project and determine complexity level. Entry point for the Memory Bank system.',
        inputSchema: {
          complexity: z.string().refine(val => ['1', '2', '3', '4'].includes(val), {
            message: 'Complexity must be 1, 2, 3, or 4'
          }),
          task_description: z.string().optional()
        }
      },
      async (args) => {
        return await (this.tools.vanModeTool.handler as any)(args);
      }
    );
  • TypeScript type definition for van_mode input parameters.
    interface VanModeInput {
      complexity: '1' | '2' | '3' | '4';
      task_description?: string;
    }
  • JSON Schema definition for van_mode tool input validation, matching the TypeScript interface.
    inputSchema: {
      type: 'object',
      properties: {
        complexity: {
          type: 'string',
          enum: ['1', '2', '3', '4'],
          description: 'Level 1: Quick bug fix, Level 2: Simple enhancement, Level 3-4: Complex features'
        },
        task_description: {
          type: 'string',
          description: 'Description of the task to be implemented'
        }
      },
      required: ['complexity']
    },
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 initialization and complexity determination, but doesn't describe what happens during initialization, whether this creates persistent resources, what permissions might be required, or what the expected output looks like. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 appropriately concise with two clear sentences that efficiently convey the core purpose and context. It's front-loaded with the main function and follows with additional system context without unnecessary elaboration.

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?

For a tool with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what the tool returns, how parameters affect behavior, or provide enough context about the Memory Bank system to understand the tool's role within it. The description leaves too many unanswered questions for effective tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage for 2 parameters, the description provides no information about what 'complexity' or 'task_description' parameters mean, their expected formats, or how they influence the tool's behavior. The description mentions 'determine complexity level' which hints at the complexity parameter but doesn't explain its semantics or relationship to the tool's function.

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 'Initialize project and determine complexity level' which provides a general purpose, but it's vague about what 'project' refers to and what 'complexity level' means. It mentions being an 'Entry point for the Memory Bank system' which adds some context, but doesn't clearly distinguish this from sibling tools like creative_mode or plan_mode that might also initialize projects.

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 explicit guidance on when to use this tool versus alternatives. While it mentions being an 'entry point', it doesn't specify when to choose van_mode over other entry points or sibling tools, nor does it outline any prerequisites or exclusions for usage.

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/nicavcrm/memory-bank-mcp'

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