Skip to main content
Glama
ipospelov

Memory Bank MCP Server

analyze_project_summary

Analyze project summaries to generate structured content suggestions for memory banks, helping preserve context in AI assistant environments.

Instructions

Analyze a project summary and provide suggestions for Memory Bank content.

Args:
    project_summary: A summary of the project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_summaryYes

Implementation Reference

  • The handler implementation for the analyze_project_summary tool. It is registered via the @mcp.tool() decorator. The function takes a project_summary string but currently ignores it and returns a static multi-line string providing suggestions for Memory Bank files structure and next steps.
    @mcp.tool()
    async def analyze_project_summary(project_summary: str) -> str:
        """Analyze a project summary and provide suggestions for Memory Bank content.
        
        Args:
            project_summary: A summary of the project
        """    # Extract potential project name (first few words)
        
        return f"""Based on your project summary, here are suggestions for your Memory Bank:
    
    ### Core Files (Required)
    1. `memory_bank_instructions.md`
        - Instructions for the Memory Bank
        - Describes how to use the Memory Bank
        
    2. `projectbrief.md`
       - Foundation document that shapes all other files
       - Created at project start if it doesn't exist
       - Defines core requirements and goals
       - Source of truth for project scope
    
    3. `productContext.md`
       - Why this project exists
       - Problems it solves
       - How it should work
       - User experience goals
    
    4. `activeContext.md`
       - Current work focus
       - Recent changes
       - Next steps
       - Active decisions and considerations
       - Important patterns and preferences
       - Learnings and project insights
    
    5. `systemPatterns.md`
       - System architecture
       - Key technical decisions
       - Design patterns in use
       - Component relationships
       - Critical implementation paths
    
    6. `techContext.md`
       - Technologies used
       - Development setup
       - Technical constraints
       - Dependencies
       - Tool usage patterns
    
    7. `progress.md`
       - What works
       - What's left to build
       - Current status
       - Known issues
       - Evolution of project decisions
    
    ## Files Location:
    All files must be located in the 'memory-bank/' directory
    
    ## Next Steps:
    1. Create 'memory-bank/' directory
    2. Fetch and create 'memory_bank_instructions.md' file as is without any edits 
    3. Create the core files using our templates
    4. Fill in the details based on these suggestions
    5. Update regularly as your project evolves
    6. Ensure details accurately reflect your project context and current state"""
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 states the tool analyzes and provides suggestions, but doesn't describe how this works (e.g., is it AI-based, rule-based?), what the suggestions might include, or any constraints like rate limits, permissions needed, or output format. This leaves significant gaps in understanding the tool's 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 concise and well-structured, with the purpose stated upfront and parameter details in a clear 'Args' section. Both sentences earn their place by defining the tool's function and its single parameter. However, it could be slightly improved by integrating the parameter explanation more seamlessly into the main description.

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 this tool's complexity. It doesn't explain what the suggestions look like, how they're formatted, or any behavioral traits. For an analysis tool with no structured output, more detail on the return value and process is needed to adequately guide an agent.

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 0%, so the description must compensate. It adds minimal semantics by explaining 'project_summary' as 'A summary of the project', which clarifies the expected content but lacks details on format, length, or quality requirements. This provides some value beyond the bare schema but doesn't fully address the coverage gap, warranting a baseline score.

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: 'Analyze a project summary and provide suggestions for Memory Bank content.' It specifies the verb ('analyze') and resource ('project summary'), and indicates the output domain ('Memory Bank content'). However, it doesn't explicitly differentiate from sibling tools like 'generate_memory_bank_template' or 'get_memory_bank_structure', which prevents a perfect score.

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 the sibling tools or specify contexts where this analysis is preferred over generating templates or retrieving structures. The only implied usage is when a project summary is available, but this is too vague for effective 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/ipospelov/mcp-memory-bank'

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