Skip to main content
Glama
mixelpixx

meMCP - Memory-Enhanced Model Context Protocol

memory_optimize

Optimizes memory usage in LLMs to enable continuous learning and knowledge retention across sessions through the Model Context Protocol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler logic for the 'memory_optimize' tool. Parses input arguments and orchestrates the optimization process by calling optimizeSystem.
    async handleOptimize(args) {
      try {
        const { rebuildIndexes = true, compactStorage = true, rebuildSemantic = true } = args;
        
        const optimizeResult = await this.optimizeSystem({
          rebuildIndexes,
          compactStorage,
          rebuildSemantic,
        });
        
        return {
          content: [
            {
              type: 'text',
              text: `⚡ **Optimization Complete**\n\n**Rebuilt Indexes:** ${rebuildIndexes ? 'Yes' : 'No'}\n**Compacted Storage:** ${compactStorage ? 'Yes' : 'No'}\n**Rebuilt Semantic Index:** ${rebuildSemantic ? 'Yes' : 'No'}\n**Duration:** ${optimizeResult.duration}ms\n**Storage Saved:** ${optimizeResult.spaceSaved || 'N/A'}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error optimizing system: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema defining parameters for the memory_optimize tool.
      type: 'object',
      properties: {
        rebuildIndexes: {
          type: 'boolean',
          description: 'Rebuild all search indexes',
          default: true,
        },
        compactStorage: {
          type: 'boolean',
          description: 'Compact storage files',
          default: true,
        },
        rebuildSemantic: {
          type: 'boolean',
          description: 'Rebuild semantic search index',
          default: true,
        },
      },
    },
  • Registers the 'memory_optimize' tool on the server with name, description, schema, and handler function.
    server.registerTool(
      'memory_optimize',
      'Optimize the memory system performance and storage',
      {
        type: 'object',
        properties: {
          rebuildIndexes: {
            type: 'boolean',
            description: 'Rebuild all search indexes',
            default: true,
          },
          compactStorage: {
            type: 'boolean',
            description: 'Compact storage files',
            default: true,
          },
          rebuildSemantic: {
            type: 'boolean',
            description: 'Rebuild semantic search index',
            default: true,
          },
        },
      },
      async (args) => {
        return await this.handleOptimize(args);
      }
    );
  • Core helper method that performs the actual optimization tasks like rebuilding indexes and measures performance.
    async optimizeSystem(options = {}) {
      try {
        const startTime = Date.now();
        const { rebuildIndexes, compactStorage, rebuildSemantic } = options;
        
        if (rebuildIndexes) {
          await this.factStore.rebuildIndexes();
        }
        
        if (rebuildSemantic) {
          this.factStore.rebuildSemanticIndex();
        }
        
        const duration = Date.now() - startTime;
        
        return {
          duration,
          spaceSaved: null,
          indexesRebuilt: rebuildIndexes,
          semanticRebuilt: rebuildSemantic,
          storageCompacted: compactStorage,
        };
      } catch (error) {
        throw new Error(`Failed to optimize system: ${error.message}`);
      }
  • Top-level registration in MemoryTools that invokes MemoryManagement.registerTools, indirectly registering memory_optimize.
    async registerTools(server) {
      // Register tools from modular components
      this.operations.registerTools(server);
      this.queryHandler.registerTools(server);
      this.streamingTools.registerTools(server);
      this.management.registerTools(server);
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/mixelpixx/meMCP'

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